Why is Get written in front of many classes almost all the time, is there a reason?

Question

So, for a while now that I'm a tutorial, I wrote Set before Get in my classes.

public class Foo
{
  public string Name { set; get; }
}

I never had any problems with this, and, logically, for me, the settings before making sense makes sense when reading. Although there is no difference in any way.

But almost every code example puts get in front of the set:

public class Foo
{
  public string Name { get; set; }
}

Is there a reason? Is it just a habit of people? Or are there any readable benefits that you get before setting the code more complicated than I still don't understand?

Answer 1

It comes down to personal preferences, since the compiler will implement in any case and have the same functionality.

, prop visual studio, , . , prop, Tab.

: https://msdn.microsoft.com/en-us/library/w86s7x04.aspx