Forcing an ASP.NET Application to 'stay alive'

Posted by: Rick Strahls WebLog, on 10 May 2007 | View original | NEW Bookmarked: 0 time(s)

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
Category: IIS | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 1541 | Hits: 175

Similar Posts

  • ASP.NET MVC: DevExpress Mail Demo more
  • New article: How to detect and avoid memory and resources leaks in .NET applications more
  • Export Word documents to XPS - Open XML Paper Specification format more
  • Sneak Peek: ASP.NET Splitter Control more
  • Gaia Ajax 3.6 Alpha released: Ajax GridView and Adaptive Rendering ++ more
  • Create or Manage XPDL 1.0 & 2.1 packages using Aspose.Workflow more
  • Application Identifiers (AI) for EAN-128 barcode generation more
  • Auto-Start ASP.NET Applications (VS 2010 and .NET 4.0 Series) more
  • ASP.NET MVC - Is WebForms the VisiCalc of Web Development? more
  • CodeDigest.Com - Articles,FAQs, Codes, News - Aug,2009 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