Well I've had this problem awhile.. where if you move over to Vista and IIS 7 you'll notice that your Debug sessions timeout very quickly, 90 seconds to be exact.
It's very annoying. I had once went through my app pool changing every time value I found to something higher just to fix it for the moment, which is a bad idea. I usually like to know why something happens and figure how to fix it properly.
So I came across a forum article on asp.net written by jshallard.
Here is the solution for fixing your Debugging Timeout Issue:
I went with the first option, I like to debug forever
In IIS 7 go to the Application Pools and select the Advanced Settings for the pool which you process runs in. In the Process Model section you can do one of two things;
* Set the Ping Enabled property to False. This will stop IIS checking to see if the worker process is still running and keep your process alive permanently (or until you stop your debugged process)
* If you prefer to allow IIS to continue the monitoring process then change the Ping Maximum Response Timeout value to something larger than 90 seconds (default value).
4d505379-1ea5-45a2-a1f0-43eae53728c5|4|5.0
Operating Systems, Troubleshooting, Visual Studio
vista, iis7, visual studio, timeout, debug, debugging timeout