Today, for any .Net development project, there are best practices that could be applied. The best practices provide a .Net developer to learn techniques, standards and conventions that are sharply realistic, focused and helpful in achieving results and steering clear of impractical and unproven recommendations. Furthermore, practices cover principles that development experts agree upon and the correct ways in developing software.
.Net development best practices include automated testing, continuous integration, code analysis and automated deployment. Regardless if the solution is from an open and free source or a commercial one, a .Net developer learns how to acquire continuous integration server that runs and executes builds each time the code changes. A developer could write more maintainable and clearer automated testing code that aims in prevention and helping the project succeed.
Best .Net development practices that a .Net developer learns include the following:
1. Real-world approaches to automated testing, continuous integration and more.
2. Guidance from minimal, vital approach all the way to what is necessary in order to deliver the highest quality levels and effectiveness.
3. Tricks and tips to clear hurdles that keep others from putting common sense ideas to common practice.
4. You learn how to build automated tests that are easier to maintain, write and focused on making certain the code under test will work the way it is meant to work.
5. How to write common automated deployment script deploying to all target environments.
6. How to do meaningful code analysis that provides the type of information you could take action.
When you move an application to production environment for the first time, it would be a good idea to generate new encryption keys, including decryption key, machine validation key and other custom keys that the application could be using. The encrypt sensitive sections of the web.config includes connection machine key and connection strings sections. Best practices also allow the developer to use trusted SQL connections and set retail in the systemconfig. When you set up a new site for the first time, never share an existing application pool but instead create a new application pool that could be used only by the new web app.
When you create an application pool, set memory limit instead of the time limit which is set by default. .Net Development has a great whitepaper that explains its value. Creating an application offline provides a wonderful way to take an app offline in a user-friendly way while at the same time fixing major issues as well. Moreover, it forces and application restarts in the event you forget to do this for deployment.
It is easy to commit mistakes when you deploy any kind of software, particularly with software that utilizes configuration files that may differ between the development, production environments and staging. You could fine tune the process as required but never let a simple typo bring your site down. Aside from making certain that .Net is configured in a debug mode, you should also make sure that the assemblies aren’t debug assemblies.