Why is there String/string and Object/object in C#?

Question

Possible Duplicate:
String vs string in C#

I know there is no difference between using string and String. But, why is there the option in C#? Is it the same for object and Object?

EDIT

Note, that I am asking why.

dupe: http://stackoverflow.com/questions/215255/string-vs-string-in-c — Steven Evers, Jun 23 '10 at 20:37
I've seen this question, but the answers didn't answer my question, which is the "why", not the "what" and "how". Is this really a dupe, or just a vote-to-close-dogpile-without-reading-the-question? If the answer can be found on the other page, please point me to it. Femaref and Daryl give answers below for my question. — Chris, Jun 23 '10 at 20:58

score 5 · Accepted Answer · answered Jun 23 '10 at 20:38

In the MS implementation of the C# standards, string maps to System.String and object maps to System.Object. In other implementations, this could map to other classes. So if you use string and object, you are on the safer side if you should ever compile it with another compiler.

score 1 · Answer 2 · edited Jun 25 '13 at 19:17

1

string is just an alias for System.String. It is just a shorthand the same way that int is shorthand for System.Int32.

edited Jun 25 '13 at 19:17

Dan Fox

1,643
15
10

answered Jun 23 '10 at 20:40

Daryl

66
2

Why is there String/string and Object/object in C#?

2 Answers2