By default, debugging a website or web project within Visual Studio bring up the built-in server of Visual Studio. But, we do have a problem to change the server to an IIS instance. I recently switched to debugging on IIS on my Windows 2008 Server Machine. Debugging works fine. The only problem is that if your code hit some breakpoint and if you leave the program in ‘break’ mode for more than 90 seconds, Visual Studio shows the following message:
After a bit tweaking around in the new IIS interface, I got the solution:
Open Internet Information Services (IIS) Manager.- From the server tree (the item with the name as the server name), choose Application Pools.
- Choose the Application Pool corresponding to your testing IIS website (usually it has the same name as your IIS website)
- Right-click and choose Advanced Settings.
- From the Process Model node, change the Ping Maximum Response Time (seconds) to a comfortably higher value (I have set the value to 900 seconds which is 15 minutes).
Alternatively, you can also set the Ping Enabled property to False.
Apparently what happens is that the server keeps pinging the worker process and waits for a response. When in debugging mode, the worker process is affectively suspended, which results in the ping not being responded.
Cool post - was looking exactly for this.
ReplyDeleteme too ;) thanks
ReplyDeleteThank you thank you!
ReplyDeleteAwesome! No more copying to notepad for me!
ReplyDeleteThank you sharing that information. This is exactly what I was looking for.
ReplyDeleteAwesome..! Exactly what I was looking for.
ReplyDeleteThank you very much. It solved my problem too.
ReplyDeleteI was looking exactly for this, thank you :)
ReplyDelete