Migrating asp.net website from IIS6 to IIS7 - Debugging differences
العربية
български
català
中文
čeština
dansk
Nederlands
eesti
suomi
français
Deutsch
Ελληνικά
עברית
हिंदी
magyar
Bahasa Indonesia
italiano
日本語
한국어
latviešu
lietuvių
norsk
polski
Português
română
русский
slovenčina
slovenski
español
svenska
ไทย
Türkçe
українська
Tiếng Việt
I recently migrated an application from IIS6 to IIS7. I've noticed two distinct differences and was wondering if someone could shed some light on them:
When I attach the debugger to the w3wp.exe process, it seems that the request times out much quicker than it did with XP. I set the executionTimeout attribute of the httpRuntime element in the web.config to be 864000 in hopes that it would execute for a very long time. This has not helped and I'm open to suggestions for how to allow for longer debugging sessions.
Answer |
For #1, you need to turn off the "Ping Enabled" setting in the Advanced Properties for the application pool. Otherwise, if you sit on a breakpoint, the process can't respond to IIS's ping and it believes the process is hung and recycles the app pool. You probably want to turn off the idle timeout as well.
For #2, I'm not sure; even with Rick's answer it sounds like it should be working as you intend.