Question: When assigning a default default-value to a field (here false to a bool), FxCop says:

```
Resolution   : "'Bar.Bar()' initializes field 'Bar.foo' 
               of type 'bool' to false. Remove this initialization 
               because it will be done automatically by the runtime."

```

Now, I know that code as `int a = 0` or `bool ok = false` is introducing some redundancy, but to me it seems a very, very good code-practice, one that my teachers insisted on righteously in my opinion.

Not only is the performance penalty very little, more importantly: relying on the default is relying on the knowledge of each programmer ever to use a piece of code, on every datatype that comes with a default. (DateTime?)

Seriously, I think this is very strange: the very program that should protect you from making all too obvious mistakes, is suggesting here to make one, only for some increased performance? (we're talking about *initialization code* here, only executed once! Programmers who care that much, can of course omit the initialization (and should probably use C or assembler :-) ).

Is FxCop making an obvious mistake here, or is there more to it?

> 
> Two updates :
> 
> 
> 1. This is not just my opinion, but what I have been taught at university
> (Belgium). Not that I like to use an
> [*argumentum ad verecundiam*](http://philosophy.lander.edu/logic/authority.html), but
> just to show that it isn't just my
> opinion. And concerning that:
> 2. My apologies, I just found this one:
> 
> 
> [Should I always/ever/never initialize object fields to default values?](https://stackoverflow.com/questions/636102/should-i-always-ever-never-initialize-object-fields-to-default-values)
> 
> 
>

Answer: 
There can be significant performance benefits from this, in some cases. For details, [see this CodeProject article.](http://www.codeproject.com/KB/dotnet/DontInitializeVariables.aspx?fid=182387&df=90&mpp=25&noise=3&sort=Position&view=Quick&select=1112738)

The main issue is that it is unnecessary in C#. In C++, things are different, so many professors teach that you should always initialize. The way the objects are initialized has changed in .NET.

In .NET, objects are always initialized when constructed. If you add an initializer, it's possible (typical) that you cause a double initialization of your variables. This happens whether you initialize them in the constructor or inline.

In addition, since initialization is unnecessary in .NET (it always happens, even if you don't explicitly say to initialize to the default), adding an initializer suggests, from a readability standpoint, that you are trying to add code that has a function. Every piece of code should have a purpose, or be removed if unnecessary. The "extra" code, even if it was harmless, suggests that it is there for a reason, which reduces maintainability.
FxCop has to provide rules for everyone, so if this rule doesn't appeal to you, just exclude it.

Now, I would suggest that if you want to explicitly declare a default value, use a constant (or static readonly variable) to do it. It will be even clearer than initializing with a value, and FXCop won't complain.

```cs
private const int DEFAULT_AGE = 0;

private int age = 0; // FXCop complains
private int age = DEFAULT_AGE; // FXCop is happy

private static readonly DateTime DEFAULT_BIRTH_DATE = default(DateTime);

private DateTime birthDate = default(DateTime); // FXCop doesn't complain, but it isn't as readable as below
private DateTime birthDate = DEFAULT_BIRTH_DATE; // Everyone's happy

```