Taking an ASP.NET application offline

Posted by: Rick Strahls WebLog, on 12 Jul 2006 | View original | NEW 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
Category: ASP.NET | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 2302 | Hits: 352

Similar Posts

  • New article: How to detect and avoid memory and resources leaks in .NET applications more
  • Sneak Peek: ASP.NET Splitter Control more
  • Gaia Ajax 3.6 Alpha released: Ajax GridView and Adaptive Rendering ++ more
  • Announcing the Microsoft AJAX CDN more
  • Announcing the WebsiteSpark Program more
  • Health Monitoring and ASP.NET MVC more
  • Telerik Releases New Controls for Silverlight 3 and WPF more
  • Avoid Entrenched Dependencies more
  • Eloquera DB 2.1 is released (.NET object database) more
  • Raleigh Code Camp this Saturday 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