Some best practices for C# developers

Here is some best practices for C# developers.

1. Check the C# source files with StyleCop – (http://code.msdn.microsoft.com/sourceanalysis) – StyleCop analyzes C# source code to enforce a set of style and consistency rules. It can be run from inside of Visual Studio or integrated into an MSBuild project.
2. Check the assemblies with FxCop – (http://msdn.microsoft.com/en-us/library/bb429476(VS.80).aspx) – FxCop is an application that analyzes managed code assemblies (code that targets the .NET Framework common language runtime) and reports information about the assemblies, such as possible design, localization, performance, and security improvements.
3. Unit Test applications with NUnit – (http://nunit.org) – NUnit is a unit-testing framework for all .Net languages. For testing ASP.Net pages there an extension of NUnit is available it is called NUnitAsp – (http://nunitasp.sourceforge.net/) , but the problem in NUnitAsp is this project is officially dead. And for unit testing Windows forms White (http://white.codeplex.com) and NUnit.
4. Use CLR Profiler -(http://www.microsoft.com/downloads/details.aspx?familyid=FD02C7D6-5306-41F2-A1BE-B7DCB74C9C0B&displaylang=en) – The CLR Profiler allows developers to see the allocation profile of their managed applications.
5. Use latest .Net framework features, like LINQ, Extention methods, Partial methods, Simple Properties etc.( http://www.microsoft.com/net/)