When I first installed Windows Vista with IIS 7 I have started to notice that ASP.NET debugger tends to time-out very often. Previously I hadn't noticed such a behavior when I was using Windows 2003 with IIS 6. I really cannot tell if it was there or not, because I sometimes tend to dismiss this kind of issues if they are not very painful.

Sometimes however the debugger timeout IS painful. Fortunately the problem is easily solved. I have found the solution provided by jshallard on ASP.NET's forum:

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).

I've tried the second option and it worked.

Add to del.icio.us