where I can find Coding Conventions for C#?

[Lost User]

thx gicio

[Nish Nishant]

I would be surprised if there are any non-MS conventions out yet! Nish

---

The posting stats are now in PDF:- http://www.busterboy.org/codeproject/ Feel free to make your comments. Updated - May 04th, Saturday

[Tom Archer]

I'm assuming you're referring to naming conventions. If so, there aren't any that are written in stone at this point. I cover this in the first edition of Inside C#, but to summarise that information, a mixture of camel (lowercase) and Pascal (mixed case string with an upper case letter) casing are used. Pascal naming is generally used on method names and camel casing is used with variables. Cheers, Tom Archer Author, Inside C# Author, Visual C++.NET Bible A total abstainer is one who abstains from everything but abstention, and especially from inactivity in the af

[James T Johnson]

As Tom pointed out camel and Pascal casing are commonly used. I use camel casing for private objects (fields, properties, methods, and local variables). I use Pascal casing for protected/public objects (fields, properties, methods). My style changes from time to time though; at one point I was prefixing private variables with an underscore. James Simplicity Rules!

[Nick Parker]

On another note for notation... I have read that Microsoft is dropping the idea of Hungarian notation for C#, all except for the i before the declaration of an interface. Nick Parker

[Tom Archer]

Yes, hungarian notation is definitely being played down by MS. Of course, since we don't see any source code any more (unlike with MFC) it really doesn't matter :) Cheers, Tom Archer Author, Inside C# Author, Visual C++.NET Bible A total abstainer is one who abstains from everything but abstention, and especially from inactivity in the af

[Nick Parker]

Tom Archer wrote: since we don't see any source code any more (unlike with MFC) it really doesn't matter I don't think this means we should start naming our variables strNumber and iWord however. :) Nick Parker

[Tom Archer]

My point was the opposite; that we are no longer bound by an underlying framework to accept that framework's naming conventions. Cheers, Tom Archer Author, Inside C# Author, Visual C++.NET Bible A total abstainer is one who abstains from everything but abstention, and especially from inactivity in the af

[Nick Parker]

I know Tom, I was only giving you a hard time, sorry :-D Nick Parker

[Tom Archer]

Sorry mate. It's late and I am sooooooooo over this chapter :) Cheers, Tom Archer Author, Inside C# Author, Visual C++.NET Bible A total abstainer is one who abstains from everything but abstention, and especially from inactivity in the af

[Nick Parker]

No problem Tom, let me ask you a question. Now that I see you have/are written/writing a book on Visual C++.NET, which language would you prefer to write an enterprise application in if asked to use the .NET Framework? Please don't say Fortran.NET or COBOL.NET :-D Nick Parker

[Tom Archer]

Actually, the VC++ book is an MFC book. However, I've done enough in Managed Extensions that I would seriously think about combining MFC and Managed Extensions. MFC for the UI simply because I've used it for 10 years and ME for the cool classes .NET has to offer. I'm not saying I would do that, but I'd give it some serious considerations under the right circumstances - especially if time was a major issue. Cheers, Tom Archer Author - Inside C#, Visual C++.NET Bible A total abstainer is one who abstains from everything but abstention, and especially from inactivity in the af

[tomiga]

As far as I know there is an appendinx in C# specification. (You can find it in your .NET installation folder in C#/C# langugae specification.doc :) Tomiga