n a perfect world, once a web application has been deployed and is live on the Internet or intranet, it will never experience any downtime. However, this is not very realistic in the real world because most applications grow and change and get updated over time. For example, as users interface with the application they may unearth bugs, or they may provide suggestions for new features or ways to enhance the user experience. After squashing those bugs and implementing the requested enhancements, the updated code base needs to be deployed to the production environment. This may involve updating ASP.NET pages, configuration files, making database modifications, and so on.
When updating a web application that’s currently in production, it is best to take the application offline so that users understand that the application is being worked on. This can be accomplished in a variety of ways, from simply stopping the web server software to displaying a web page that informs the user that the site is offline for maintenance. What you don’t want to do is have the application appear to work, only to have some error pop up later because you are in the middle of updating the production server. This is a sure-fired way to frustrate your users.
In this article we will discuss options for taking a web application offline. Read on to learn more…
ASP.Net November 8th, 2007