Forcing an ASP.NET Application to 'stay alive'

Posted by: Rick Strahls WebLog, on 10 May 2007 | View original

This post in the 'stupid pet tricks' category I suppose - it's not one of the things that you need to do every day, but if you need to run an application that requires that your ASP.NET application stays up and running without the discontinuity of AppDomain or worker process shutdowns this can be useful. First some background on the scenario. I'm working on a small project for a customer that deals with a background scheduler that's running continuously and checks the contents of a POP3 box at intervals....

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
  • Recipe: Enabling Windows Authentication within an Intranet ASP.NET Web application more
  • Blogging from Tech Ed 2006 - Stefan Shakow on ASP.NET - level 400 more
  • More about exception handling and new coolness from Joshua Flanagan more
  • Go XBAP, WPF/E and Big Screen Photos! Aussie Aussie Aussie... more
  • SDC Sessions - THE CODE more
  • Tech Ed 2006 Summary 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