IIS7 - Publishing

Re: IIS 5 to IIS7

bapo_10@hotmail.com — Sun, 28 Jun 2009 21:40:29 GMT

Yes I have quizzed them along these lines - thankyou for the possible cause.

Re: IIS 5 to IIS7

steve schofield — Sun, 28 Jun 2009 01:07:12 GMT

sounds like your provider has a policy of shutting down if there is no activity after a set amount of time. This is common in shared hosting, it preserves resources on the server. I'd suggest contacting them and see if they have a policy on the application pool.

IIS 5 to IIS7

bapo_10@hotmail.com — Sat, 27 Jun 2009 23:05:11 GMT

I have written an application using ASP.NET 3.5, XP and IIS 5. The application runs fine on my local machine. I can connect to the app - the worker process fires up and I am able to open as many IE browsers against it as I wish. I can close them - open them at will and the application behaves as if I am connecting to one instance of IIS (not sure about terminology here)?

I have put it on a third party web server. The application runs fine while I have the browser open. if I close the browser and reopen - say 5 minutes later it connects to the instance I set running. If I leave it an hour after closing all browsers from my client to the remote web server it seems as if it starts a new instance. The one I set running has been lost?

What am I doing wrong or what do I need to ask the guys who run the web site to set?

All help appreciated - I stuck here!