Question

I saw multiple examples in MSDN that uses to declare the internal fields at the end of the class. What is the point?

I find this a little embarrassing, because each time Visual Studio adds a method it adds it to the end of the class, so there is need every time to move it…

class A
{
  public A(){}
  // Methods, Properties, etc ...

  private string name;
}

class A
{
  private string name;

  public A(){}  
  // Methods, Properties, etc ...
}

Answer 1

In C++, it makes sense to put the public interface of the class at the top, so that any user of the class can open up your header file and quickly see what’s available. By implication, protected and private members are put at the bottom.

In C# and Java, where interface and implementation are completely intertwined, people would probably not open your class’s source code to see what’s available. Instead they would rely on code completion or generated documentation. In that case, the ordering of the class members is irrelevant.