Why does C#.Net allow the declaration of the string object to be case-insensitive?
String sHello = "Hello";
string sHello = "Hello";
Both the lower-case and upper-case S of the word String are acceptable and this seems to be the only object that allows this.
Can anyone explain why?
string is a language keyword while System.String is the type it aliases.
Both compile to exactly the same thing, similarly:
int is System.Int32long is System.Int64float is System.Singledouble is System.Doublechar is System.Charbyte is System.Byteshort is System.Int16ushort is System.UInt16uint is System.UInt32ulong is System.UInt64I think in most cases this is about code legibility - all the basic system value types have aliases, I think the lower case string might just be for consistency.
Further to the other answers, it's good practice to use keywords if they exist.
E.g. you should use string rather than System.String.
"String" is the name of the class. "string" is keyword that maps this class.
it's the same like
... and so on...
"string" is a C# keyword. it's just an alias for "System.String" - one of the .NET BCL classes.
"string" is just an C# alias for the class "String" in the System-namespace.
string is an alias for System.String. They are the same thing.
By convention, though, objects of type (System.String) are generally refered to as the alias - e.g.
string myString = "Hello";
whereas operations on the class use the uppercase version e.g.
String.IsNullOrEmpty(myStringVariable);
I use String and not string, Int32 instead of int, so that my syntax highlighting picks up on a string as a Type and not a keyword. I want keywords to jump out at me.
STRINGorstrinGor anything else. Secondly, it is not the only type that has an alias:objectis an alias forObject;boolis an alias forBoolean;doubleis an alias forDouble, etc. Incidentally,voidis also an alias forVoid, but C# doesn’t let you useVoid...