Bits.Bytes.

Isn’t this already provided by the IDE in VS2005? You can type Prop string foo and it will generate the Property for you…it’s a code snippet (I think that’s the term)

It is a bit odd that the automatic properties (so far) generate an essentially inaccessible private field. I was hoping that it would just be a shortcut for the property and field declaration (e.g. Age would generate ‘int m_Age;’ or something), but instead it generates an otherwise inaccessible ‘k__AutomaticallyGeneratedPropertyField0′. This also means that both a getter and a setter are required, since there is otherwise no way to set the value.

So if you have properties that are just used in classes that are passed around that contain configuration or other “just data” uses, then it’s a fine syntax, but…

I’d love it if they could provide a slight variation on the theme to allow an actual declared variable and thus allow get-only or set-only, e.g.

public int Age(int m_Age) { get; set; }
or
public int Age(m_Age) { get; set; }
or
public int Age { int m_Age; get; set; }

I’d take the attributes, too, though I understand the one-line appeal.

– Ritchie

I think that this is useful only for the stupid standard C# serialization, which can serialize only properties and no attributes. If I have a read/write member I see no reason to make it a property. I prefer to write:
class Person
{
public string Name;
}
which can be changed ususally without breaking any code to
class Person
{
private string name;
public string Name
{
get { return name; }
set { name = value; }
}
}