
standards
Get flash to fully experience Pearltrees
Best Practices for ASP.NET MVC - ASP.NET and Web Tools Developer Content Team - Site Home - MSDN Blogs
[This post is based on a document authored by Ben Grover (a senior developer at Microsoft). It is our intention to integrate this information into the MVC 3 documentation on MSDN.Blog - CopyPasteKiller - Free Code Similarity Finder
So I just published CopyPasteKiller , a free tool that helps .Net developers working with large code bases find all the places that another developer used the time honored practice of Copy-Paste Inheritance.This coding style guide only applies to how to structure and name your classes, variables, functions, etc, not on how to document them.
Documentation / JavaScript Style Guide
ASP.NET MVC View Best Practices – Keep logic out of your views | Arrange Act Assert
C# now has support for named parameters at the call site.
Use Optional Parameters to Minimize Method Overloads
Has anybody published any C# 4 coding standards / guidelines / style guides? - Stack Overflow
Home | Email Standards Project
The Email Standards Project works with email client developers and the design community to improve web standards support and accessibility in email. Our goal is to help designers understand why web standards are so important for email, while working with email client developers to ensure that emails render consistently. This is a community effort to improve the email experience for both designers and readers alike. What you can do to support the Email Standards Project Whether it's spreading the word about our cause, helping out with additional research or telling us the secret handshake for the Gmail team, we'd love your help.NHibernate Best Practices with ASP.NET, 1.2nd Ed. - CodeProject
Author's note added June 11, 2008 - Announcement of S#arp Architecture Thankfully, technologies evolve over the years. Accordingly, Microsoft has introduced ASP.NET MVC as an alternative to classic ASP.NET.As we home in on the release of SharePoint 2010, I wanted to write down a couple of thoughts for posterity on SharePoint 2007 development, mainly for my benefit. One of the reasons for doing this is because I’ve been working with the SP2010/VS2010 Tech Previews recently, and whilst I’ve not done a full “compare and contrast” exercise, I can certainly see that in the future I will want to reference back to how I liked to handle something in the SharePoint 2007 world, and more importantly, why.

