Hi,
I think what you want is your code using best practices for .NET Framework
as recommeded by microsoft.When ever we are talking about bad coding one tool
comes to our mind that is FXCop .Those who are new to FXCop , it is a free
code analysis tool (open source) from Microsoft which analyze your compiled
.NET assemblies for compliance with recommended programming practices. Let me
take you a brief history of FXCop .The FX in FXCop stands for Framework as in
.NET Framework. Actually its original name was UrtCop (Universal Run Time )
the old name of CLR.The full name is Framework Cop and in short we call it as
FXCop. The next question how and why FXCop . FXCop was created to address the
goal of ensuring a consistent look and feel for a brand-new public API of
.NET Framework. During the development process, it became clear the
application was also useful for uncovering API usage and general correctness
problems. The tool is possible due to key features of the .NET Framework that
make signatures-and even Intermediate Language code itself-easily
discoverable. FxCop is a case study of the time-to-develop benefits of the
.NET Framework. We're pretty proud that it has achieved functionality in an
extremely short development time-functionality that is similar to other tools
(targeted toward unmanaged binaries).This is the way FXCop comes in
picture.You can download this tool from http://www.gotdotnet.com/team/fxcop 

ref:http://www.c-sharpcorner.com/UploadFile/akrao/CodingPractices11182005011444AM/Co
dingPractices.aspx