You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 1, 2018. It is now read-only.
HttpPlatformHandler has a startup time limit for how long it will wait for the back-end process to accept requests. Then it kills the process and tries again up to 10 times. However, if we want to debug anything at startup we usually exceed these limits so we have to override them with startupTimeLimit="3600".
Proposal: HttpPlatformHandler should ignore this time limit while the debugger is attached.
Attached to what process? The back-end process? IIS Express? Both?
The text was updated successfully, but these errors were encountered:
Fixed in the next release of HttpPlatformHandler (v1.3?).
However, we've got some tooling work to do on our side. When we switch to the .NET CLI we'll loose our DNX MITM that waits for the debbugger to attach before running user code. Tentative theory is for VS to replace this with it's own debug launcher that starts the back-end process suspended, waits for the debugger to attach, and then resumes it. The intermediate process can then exit because HttpPlatformHandler only monitors the process that is listening on the socket. @BillHiebert
HttpPlatformHandler has a startup time limit for how long it will wait for the back-end process to accept requests. Then it kills the process and tries again up to 10 times. However, if we want to debug anything at startup we usually exceed these limits so we have to override them with
startupTimeLimit="3600"
.Proposal: HttpPlatformHandler should ignore this time limit while the debugger is attached.
Attached to what process? The back-end process? IIS Express? Both?
The text was updated successfully, but these errors were encountered: