Jump to content

Microsoft guidelines for .NET-based code

- - - - -

This topic has been archived. This means that you cannot reply to this topic.
1 reply to this topic

#1
ArekBulski

ArekBulski

    Speaks fluent binary

  • Members
  • PipPipPipPipPipPipPipPip
  • 1,376 posts
The article shows .NET guidelines on how to name your classes, and code in overall. I totally agree with them, and furthermore I consider them very lean and easy to read. I recommend reading this article to everyone. :)

The author presents the guidelines from Microsoft (which I consider great) as well as his "ux" naming for controls on form. He points that IntelliSense sorts them together this way.

ZekeDragon gave me this link, I politely ask to stick this thread. Up to your decision, Jordan.

.NET Naming Conventions and Programming Standards and Best Practices - irritatedVowel.com

http://forum.codecal...=1&d=1252231422

Attached Files



#2
Guest_Jordan_*

Guest_Jordan_*
  • Guests
Very nice website. I won't stick this thread because it really contains no relevant data, just a link to relevant data. If you would summarize the standards here in this thread, I would stick it. :)

On standards, I think they are great and everyone should follow some form of standard when coding.