About Built -in Types

C# has a number of keywords such as: string, sbyte, byte, int, long etc. which are just aliases for types in the System namespace of the .NET Framework:

string -> String

sbyte -> SByte

byte -> Byte

int -> Int32

long -> Int64

As long as you have the using directive:

using System;

in your program. the C# keywords and their corresponding .NET Framework types are interchangeable and which you prefer is just a matter of taste.

Personally, I prefer to use the C# keywords as they give C# some character of its own and are unambiguous.

There's nothing to stop you declaring a class of your own called 'String' but you can't create a class called 'string'. You can create one called @string but it's not something anyone would do in practice.

You also have to remember that there are a large number of languages targetting .NET and some of these may need to use the .NET framework type names if they don't have a corresponding type of their own.

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Vulpes15y ago
Accepted answer
C# has a number of keywords such as: string, sbyte, byte, int, long etc. which are just aliases for types in the System namespace of the .NET Framework:

string -> String
sbyte -> SByte
byte -> Byte
int -> Int32
long -> Int64

As long as you have the using directive:

using System;

in your program. the C# keywords and their corresponding .NET Framework types are interchangeable and which you prefer is just a matter of taste.

Personally, I prefer to use the C# keywords as they give C# some character of its own and are unambiguous.

There's nothing to stop you declaring a class of your own called 'String' but you can't create a class called 'string'. You can create one called @string but it's not something anyone would do in practice.

You also have to remember that there are a large number of languages targetting .NET and some of these may need to use the .NET framework type names if they don't have a corresponding type of their own.
Sam Hobbs15y ago
String vs string

There are many useful previous answers too.
Banketeshvar Narayan15y ago
Thanks for clearing my concept.