Here I am still working on the WCF stuff, and now I’m trying to debug an issue (that shouldn’t exist, hence why its a bug), and as I’m in the middle of tracking it down in the design environment, I get the following helpful message from Visual Studio.  This is with IIS 7.0 btw…

I’ve encountered this a few times and each time I have to hunt for the answer, so I’m documenting it here for NEXT time.

1. Open IIS Manager (its in Administrative Tools, in Control Panel)
   
2. Expand the <computer name> node
   
3. Expand the Sites node and select the web site you are working with and click “Basic Settings…”
   
   
4. determine the Application Pool you are working with
   
   
5. Click Cancel and now click on the “Application Pools” node 
   
6. Select the correct Application Pool and click on “Advanced Settings…”
   
   
7. Find the “Process Model” section and either
   
   1. Set "Ping Maximum Response Time" to value large enough to let you finish debugging
      
      -- or --
      
   2. Set "Ping Enabled" to False
      
      NOTE: Be aware that setting Ping Enabled to false will prevent IIS from detecting / killing any other “dead” process that is running on that Application Pool.
      I recommend that you Instead make a NEW Application Pool, something like “never die” and assign your server to debug to that Application Pool.
      
8. Click OK