C# added auto-implemented properties in version 3, but Visual Basic was unable to match them at that time. With the impending release of .NET 4.0, VB has caught up in this area, but with a distinctive twist. In C#, auto-implemented properties are written as such:
public string FirstName {get; set;}
Visual Basic requires the keyword Property, which means it doesn’t need the get/set pair to distinguish it from a field. Thus auto-implemented properties in VB are only one token away from a field.
Public Property FirstName As String
For both VB and C# the property is automatically backed a private field. In C# this member has an automatically generated name such as “<FirstName>k__BackingField”. Needless to say, this field isn’t accessible using normal C# syntax. Visual Basic is far less creative, it merely takes the property name and prepends an underscore. So if you property is named “FirstName”, there will be a matching private field called “_FirstName”.
Having direct access to the backing field should make more things possible. Logic says one should be able to do things like mark the property ReadOnly and set its value in the constructor. Alas, that is not an option.
C#, despite its seeming limitation, is actually more flexible. You can mark the setter as private or protected, effectively getting the same effect as having access to the backing field.
public string FirstName {get; private set;}
A limitation for both languages is that they still don’t have any facilities for immutable objects. If you want objects where the properties and fields are all read-only and set in constructors, you still have to write the same code you would write in .NET 1.0.