Taking an ASP.NET application offline

Posted by: Rick Strahls WebLog, on 12 Jul 2006 | View original | Bookmarked: 0 time(s)

Sometimes it’s necessary to take an ASP.NET application offline. A common scenario is when you need to update the database or running some mainteanance updates that might put the application or database into an unstable state and you generally don’t want to have your customers/users accessing the site while the application is in this unstable state.   There are a variety of ways to accomplish this of course. First you can of course physically pull the plug on your Web server <g>....

Advertisement
Free Agile Project Management Tool from Telerik
TeamPulse Community Edition helps your team effectively capture requirements, manage project plans, assign and track work, and most importantly, be continually connected with each other.
Category: ASP.NET | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 3463 | Hits: 798

Similar Posts

  • Silverlight From Zero more
  • New article: How to detect and avoid memory and resources leaks in .NET applications more
  • WPF 4 (VS 2010 and .NET 4.0 Series) more
  • View and print Reporting Services Reports from Silverlight. more
  • HealthVault 0908 SDK Highlights more
  • Microsoft announced the beta release of IIS Application Warm-Up more
  • Health Monitoring and ASP.NET MVC more
  • Avoid Entrenched Dependencies more
  • Software Externalities more
  • Web Deployment Tool released to web (RTW) more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD