VB.NET Coding Guidelines from AddressOf.com

VB.NET Coding Guidelines

"Table of Contents

1. Introduction
2. Style Guidelines
2.1 Tabs and Indenting
2.2 Option Explicit / Option Strict
2.3 Block Formatting
2.4 Single line statements
2.5 Commenting
2.5.1 Copyright notice
2.5.2 Documentation Comments
2.5.3 Comment Style
2.6 Spacing
2.7 Attributes
2.8 Naming
2.9 Naming Conventions
2.9.1 Interop Classes
2.10 File Organization
2.11 Doing things the Visual Basic .NET Way
2.12 Microsoft.VisualBasic.Compatibility
2.13 Other Considerations
2.14 Special Thanks

1. Introduction

First, read the .NET Framework Design Guidelines. These guidelines exist to extend upon those guidelines for the VB.NET developer. Almost all naming conventions, casing rules, etc., are spelled out in this document. Unlike the Design Guidelines document, you should treat this document as a set of suggested guidelines. These guidelines are not to be taken a law and exist to offer guidance for people who do not have guidelines or are seeking improving upon their existing coding habits.

..."

I agree with many/most of the items in this guideline... And it's good to see I'm not the only one in the world who uses 2 spaces for my indents/tab. Four has always seemed to me to bloat the line length too much...

One of the things I don't agree with is the "m_" for private class scoped variables. I just don't like the "_", but so many people use "m_" that I might just have to get over it... sigh.

Still this guide is short, sweat and too the point, making it actually usable. ;)