Yes there is a reason for it. It is a Pascal Case naming convention
for method names that is a standard in the .NET framework.
All the types in the framework class library (FCL) follow the mentioned naming convention, and when you create some custom types or add methods to existing types you are augmenting the capabilites of the framework for your specific application needs.
Your method capitalizedLikeThis
is part of the Program
class, which has an API that follows the .NET naming conventions. For example it contains a ToString()
instance method so you could do:
var program = new Program();
Console.WriteLine(program.ToString());
So the real question is do you want to add a method to the Program class that breaks the naming convention of the existing API? Consistency is a good thing and that is why you should follow the convention.
If you want more information on this topic you can check out the only relevant book for .NET design guidelines containing naming conventions, and many other details related to the .NET framework design decisions:
http://www.amazon.com/Framework-Design-Guidelines-Conventions-Libraries/dp/0321246756
Or read the reduced MSDN article based on the book:
http://msdn.microsoft.com/en-us/library/ms229042.aspx