C# Automatic Properties

c# c#-3.0 automatic-properties
Gavin picture Gavin · Aug 18, 2009 · Viewed 20.6k times · Source

I'm a bit confused on the point of Automatic properties in C# e.g

public string Forename{ get; set; }

I get that you are saving code by not having to declare a private variable, but what's the point of a property when you are not using any get or set logic? Why not just use

public string Forename;

I'm not sure what the difference between these 2 statements is, I always thought you used properties if you wanted additional get/set logic?

Answer

MatthewMartin picture MatthewMartin · Aug 18, 2009

Properties can have code put into them without breaking contract, fields can't have code put into them without changing them to properties (and breaking the interface). Properties can be read only or write only, fields can't. Properties can be data bound, fields can't.

Related questions

Difference between Property and Field in C# 3.0+

I realize that it seems to be a duplicate of What is the difference between a Field and a Property in C#? but my question has a slight difference (from my point of view): Once I know that I will …

Read More
C# Automatic Properties - Why Do I Have To Write "get; set;"?

If both get and set are compulsory in C# automatic properties, why do I have to bother specifying "get; set;" at all?

Read More
how to override set in C# of automatic properties

I want to use auto-implemented properties, but at the same time I want to call a method every time the property is changed. public float inverseMass { get; set { onMassChanged(); inverseMass = value; } } Does the previous code make a recursive call to …

Read More