Migrating an asp.net website from IIS6 to IIS7 - Debugging Differences
I recently migrated an application from IIS6 to IIS7. I noticed two different differences and wondered if someone could shed some light on them:
When I attach the debugger to the w3wp.exe process, the request seems to time out much faster than it did with XP. I have set the executeTimeout attribute of the httpRuntime element in the web.config file to 864000 in the hope that it will run for a very long time. It didn't help, and I'm open to suggestions on how to allow longer debugging sessions.
source to share
For # 1, you need to disable the "Ping Enabled" option in the advanced properties for the application pool. Otherwise, if you are sitting on a checkpoint, the process will not be able to respond to the IIS ping, and it thinks the process hangs and recycles the application pool. You probably also want to disable idle timeout.
For # 2 I'm not sure; even if Rick responds, it sounds like he should work the way you plan.
source to share
Read Reversal Timeout . It doesn't work the way you think:
Specifies the time, in whole minutes, after which the cookie expires. The default is 30. If the SlidingExpiration attribute is true, the timeout attribute is a sliding value that expires the specified number of minutes after the last request was received. To prevent performance degradation and to avoid multiple browser warnings for users who have cookie warnings enabled, the cookie is refreshed when more than half of the specified time has passed. This can lead to a loss of accuracy. Persistent cookies do not time out.
source to share