class A
{
public int myInt {get; set;}
}

is completely rediculus and useless. Absolutely the same functionality is achieved by setting a variable like:

public int myInt;

Can anyone tell the difference?!?
…maybe there are some achivements if we are going to inherit the class

What is really new is setting one of either GET or SET to private, but that’s not completely logic of a property.

I thought they had made, and something that would be meaningfull is:

public int myInt
{ get;
set { myInt=value;
//some other stuff caused by changing the value
}
}

or

public int myInt
{ get
{ //some calculation
return result;
set;
}

So in this way you would be able to write only the part of the code that is different from “default codes” for get and set….
….I am really pissed off!

With auto-property the debugger skips the internal and goes to inspect the next statement. Pretty darn convenient.

Then typing :

public int YearBorn { get; private set; }

can be nice.

I agree that this is not the common scheme.

Automatic properties are useful, but there are drawbacks to getting into the mindset of using this. Consider that you have an automatic property – what benefit are you actually getting? How is this an improvement on just exposing a field?

You would normally want to use a property to do more than just control access to the field – so you might put some code into the property setter to notify you that the property has changed. This means that you are going to have to forgo the automatic property and actually handle it yourself.