Taking an ASP.NET application offline

Posted by: Rick Strahls WebLog, on 12 Jul 2006 | View original

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

Similar Posts

  • Tip/Trick: Show Detailed ASP.NET Error Messages to Developers (and only to Developers) more
  • August 9th ASP.NET Link-Listing more
  • Blogging from Tech Ed 2006 - Stefan Shakow on ASP.NET - level 400 more
  • Why ASP.NET 2.0 Login control doesn't work with SQL Membership provider? more
  • MSDN Webcast: Tablet PCs and Smartphones: Working Hand-in-Hand to Enable Your Mobile Workforce more
  • Recipe: Enabling Windows Authentication within an Intranet ASP.NET Web application more
  • Oracle Database ASP.NET 2.0 Provider Schema : Work In Progress more
  • XNetView runs on .net 1.1 and msde and is a Free Internet Development Framework for Mashup Applications and Mashup Systems more
  • Blogging from Tech Ed 2006 - Stefan Shakow on ASP.NET - level 400 more
  • Catalyst releases SocketTools .NET more

News Categories

.NET | ADO.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Community Server | dasBlog | 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