Windows Azure and ASP.NET MVC Migration

Chapter 7

Maintaining an ASP.NET MVC 4 Deployment on Windows Azure

CONCEPTS

IN THIS CHAPTER

• How to monitor a Windows Azure Web Site
• How to monitor a Windows Azure Cloud Service
• How to use Windows Azure tools

The life of an application begins after development, optimization, and deployment. When customers and users access the system’s features and services, they’ll notice its behavior and personality. In some cases, the reasons for a problem or behavior are obvious and you can easily correct or modify them. Other complications are more subtle and harder to understand, track, trace, and log. To track, trace and log, it was once a common practice in ASP-based websites to use print statements for debugging, or to strategically place Response.Write() commands in the file to write algorithm results and to confirm run time values.

Debugging and troubleshooting capabilities have improved greatly with the introduction of such technologies as System.Diagnostics, Tracing, ETW, Logman, Failed Request Tracing, and so on, which are built into the Windows Server environment and require no additional installations. This is important because in many environments security, release, or change management processes prevent you from installing tools and monitors or make it extremely time-consuming to deploy them. When production problems occur, it is important to move fast, so having these features on the platform by default moves debugging and diagnosis along quicker.

If you have completed all the ...