primitive types

[Mark]

What is the difference between declaring variables like ...

string strSomething;

versus

String strSomething;

My understanding is that the first uses a primitive type, and the second
creates an instance of a String class. While it likely will never make a
difference, is there reason to consider always using the primitive data type
when that's all you need? What are the best practices related to this?

Perhaps String/string is a unique case ... but bool and Boolean appear to be
similar???

Thanks in advance.

Mark

[Mattias Sjögren]

Mark,

What is the difference between declaring variables like ...

string strSomething;

versus

String strSomething;
"string" is a language keyword and an alias for System.String.
"String" and "string" should pretty much always resolve to the same
thing. You can, however, use "string" without importing the System
namespace. To use "String" you must either add "using System;" or
fully qualify it as System.String.

Perhaps String/string is a unique case ... but bool and Boolean appear to be
similar???

Yes, the same applies to int/Int32, float/Single and so on.

Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

[Mark]

Thanks Mattias. I'd assume this means that the most straight forward way to
do this is to always using string and bool rather than String and Boolean.

Correct?

Thanks again.

Mark

"Mattias Sjögren" <ma********************@mvps.org> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...

Mark,

What is the difference between declaring variables like ...

string strSomething;

versus

String strSomething;

"string" is a language keyword and an alias for System.String.
"String" and "string" should pretty much always resolve to the same
thing. You can, however, use "string" without importing the System
namespace. To use "String" you must either add "using System;" or
fully qualify it as System.String.

Perhaps String/string is a unique case ... but bool and Boolean appear to besimilar???

Yes, the same applies to int/Int32, float/Single and so on.

Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

[Rob Teixeira [MVP]]

In C#, the alias is preferred, yes. As Mattias said, it's just an alias...
the compiler actually writes the same thing behind the scenes regardless of
which one you use. If you are coming from the Java world, this isn't like
boolean vs. Boolean, where one is a primitive and the other is an "object
version" of the primitive.

-Rob Teixeira [MVP]

"Mark" <mf****@idonotlikespam.cce.umn.edu> wrote in message
news:Oh**************@TK2MSFTNGP09.phx.gbl...

Thanks Mattias. I'd assume this means that the most straight forward way to do this is to always using string and bool rather than String and Boolean.

Correct?

Thanks again.

Mark

"Mattias Sjögren" <ma********************@mvps.org> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...

Mark,

What is the difference between declaring variables like ...

string strSomething;

versus

String strSomething;
"string" is a language keyword and an alias for System.String.
"String" and "string" should pretty much always resolve to the same
thing. You can, however, use "string" without importing the System
namespace. To use "String" you must either add "using System;" or
fully qualify it as System.String.

Perhaps String/string is a unique case ... but bool and Boolean appear

to besimilar???

Yes, the same applies to int/Int32, float/Single and so on.

Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.