Our ASP.NET site uses a number of long running classes to manage data. Some of these classes are object factories and some perform other functions like collecting external data or monitoring various things. All of this works well enough except when we have a need to recycle the application pool. The startup overhead for some of these classes is somewhat high and we're also running into issues with the application not always getting shutdown correctly before the new application pool comes up.
So, my question is, what are some best practices for this type of situation? What we're considering doing is changing our long running classes to work as a Windows service and have the ASP.NET site connect to that service (probably via remoting). Is this the best approach? Are there any gotchas?
...
Go to the complete details ...