I would like to debug a website, but also cause the httpRuntime executionTimeout setting to take effect. However, the documentation says:
This time-out applies only if the debug attribute in the compilation element is False.
Is there any way to enable executionTimeout when debug="True"?
After more than a week of searching and trying various hacks, I'm confident in saying that, as of now, there is no reasonable way to have the httpRuntime executionTimeout setting take effect while the compilation debug flag is set to true.
One possible terrible hack workaround is to somehow trick the system into thinking that more than 30,000,000 seconds (just over 347 days) have elapsed, which is what executionTimeout is overridden to when debug is true.
If you use ASP.NET MVC then this may help. ASP.NET MVC (version < 4) doesn't support this timeout.
That's interesting, because I have debugging sessions timeout on me all the time when I'm just sitting there looking at the code. Is there another timeout value that is handled by IIS rather than ASP.NET?
