What is the advantage of using auto-implemented properties with the default access, instead of using public fields? [duplicate]

Answer 1

The main advantages are:

1. Future-proofing your API - If you later need logic in the getter or setter, your public API doesn't change.
2. Data binding - Most data binding frameworks only work against Properties, not Fields.

Answer 2

Pros

• Easy declaration

Cons

• Can not set a breakpoint inside set/get
• Can not have a code inside get/set
• Do not working on WPF DataBinding
• No concept like a default value for the property, as there is no default field behind it.

Pros and cons are strictly related to the project implementation.

Just a couple of hints, pretty sure others will add something else...

Answer 3

The primary reason that we don't use auto-implemented properties is for those serialization mechanisms that serialize the members and not the properties (such as binary serialization for .Net remoting).

In this case, if you have two applications that compile the same class separately and exchange a serialized copy of the class, there is no guarantee that it will deserialize correctly since you can't control the names of the private members.

Answer 4

I do not believe they will compile to the same IL, as get and set for properties are actually functions on the IL level and when dealing with reflection. Here are some reasons to do it though:

1. Reflection!
2. Serialization/Deserialization only works on public properties, not public fields.
3. Debugging, you can set break points on a get or a set, which can help to track down when the variable is accessed, specifically if you are seeing a goofy value and you don't know where it is coming from.