-
Notifications
You must be signed in to change notification settings - Fork 1
Recommended Practices
Aaron edited this page Sep 10, 2012
·
5 revisions
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.
- 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 inGlobal.asax.cs
. This keeps things cleaner and more RESTful, as you won't have to use file extensions in the URL.
- 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.
Pages in this wiki make use of the following resources throughout
- Martin, R. C., Feathers, M. C., Ottinger, T. R., Langr, J. J., Schuchert, B. L., Grenning, J. W., Wampler, K. D., ... Coplien, J. O. (2011). Clean code: A handbook of agile software craftsmanship. Upper Saddle River [etc.: Prentice Hall.
- Lowy, Juval, (July 2011). “C# Coding Standard: Guidelines and Best Practices.” (Version 2.4) www.idesign.net, © 2011 IDesign Inc.
Resources besides these will be referenced directly where they are cited.