string = "" or = string.Empty?

[Sami]

string = "" or string = string.Empty?
should is the proper way?

Sami

[Mythran]

>

I personally like to use "", because sometimes you can mistake
string.Empty for being null.
It's essentially the same thing, although there might be some
difference under the hood.
But I believe that string.Empty just does = "", so it's just one more
level of redirection (although I have to check up on the value of
string.Empty)
If you have a doubt about what something does in the .NET Framework,
just google for DotNetReflector and download it. It's a great program
that uses reflection to disassemble the IL code of any .NET assembly
(including mscorlib and the like) and then convert it to C# or some
other languages (although some code is obfuscated).

Empty is a readonly member variable of the String class which is set in
String's default constructor as an empty string literal (IE: ""). But, just
because it is a member variable does NOT mean it isn't treated differently
by the compiler and compiled into more efficient code depending on how it's
called.

HTH,
Mythran

[Peter Duniho]

On Mon, 25 Aug 2008 09:46:14 -0700, Mythran <My*****@commun ity.nospam>
wrote:

Empty is a readonly member variable of the String class which is set in
String's default constructor as an empty string literal (IE: ""). But,
just because it is a member variable does NOT mean it isn't treated
differently by the compiler and compiled into more efficient code
depending on how it's called.

In particular, because it's an interned string in a shared DLL (that is, a
DLL that can be shared across multiple processes), there is a potential
tiny savings if one uses _only_ String.Empty, in that the process won't
have to allocate that one extra emtpy string.

If you've got even one "" in your code somewhere though, that would negate
any benefit. And in any case, it's certainly not worth worrying about.

Pete