Skip to content

Latest commit

 

History

History
13 lines (8 loc) · 1.08 KB

Recommended-Practices.md

File metadata and controls

13 lines (8 loc) · 1.08 KB

This section is for items that have not quite attained broad appeal or widespread adoption it takes to be called "best" practices, but are recommended nonetheless.

ASP.NET/Ajax Architecture

When developing the web services which will be consumed by your Ajax calls, in lieu of .asmx files, .aspx WebMethods or WCF .svc files, use RequestRouters, which you can load in the Application_Start method in Global.asax.cs. This keeps things cleaner and more RESTful, as you won't have to use file extensions in the URL.

Go ahead... embrace the future!

In contrast to the IDesign standards, we recommend using the default parameters/named parameters features introduced in C# 4.0. It’s an opportunity to reduce the number of methods per class as opposed to overloaded methods. Those of us who have used JavaScript or VB or other languages that have this feature have typically missed it in C#, so it’s great to finally have it.

Windows Services

When developing Windows services, create a pre-build script to stop the running service to prevent build errors. e.g.

net stop MyService