Aug 062005
 

Most developers cringe when they hear the words “Coding Standards.” A developers coding style defines them. Their style has been molded over the years into what it is today. Telling a developer that their way is not the “right way” is difficult and sometimes taken personally.


Coding standards are, however, an important part of every project. Deciding on coding standards often happens too late when there is too much code in too many different styles. It is important to every developer to have and appreciate standards because we will “inherit” someone elses code. It would be nice if we could read it.


I recently got the chance to review David McCarter’s 53-page book titled “VSDN Tips & Tricks .NET Coding Standards.” I loved it! It combines coding standards from Microsoft and other sources (not to mention common sense) into one easy-to-read “guide.” Its focus is on Visual Studio .NET 2003 with v1.1 of the Framework. That doesn’t mean that you Beta 2 snobs can’t read it! It provides C# šŸ™‚ and VB šŸ™ examples and covers a variety of topics from indentation and word choice to event and exception handling.


I have seen most of the suggested standards in various other white papers and on MSDN. It’s a great book to compare against your company or personal coding standards. Not everything in this book will make sense to every shop. Personally, I found only a few items that I don’t already use (one of which being the use of Event Accessors instead of using public event member variables.)


Definitely worth reading. Find out more at http://www.vsdntips.com

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

(required)

(required)

Time limit is exhausted. Please reload the CAPTCHA.