Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Propogate ExecutionContext when run in IIS

See original GitHub issue

Moving bug from the codeplex as it is still an issue for us with no easy solution.

If you develop OWIN middleware for monitoring you need to use ThreadAsync or CallContext to keep the context across the async/await. And it is working fine. However if you try to use the same middleware when hosting your application in IIS - it doesn’t propagate the context any longer.

Even better if there will be a possibility to set the context from HttModule’s Begin callback that will be preserved to the controller execution.

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:20 (9 by maintainers)

Top GitHub Comments

1reaction

maximcuscommented, Oct 25, 2018

Yes that works if the handler completes synchronously. If it’s async then it won’t flow to the controller.

@davidfowl , can you please elaborate on this. Did you mean that ExecutionContext can be lost between PreRequestHandlerExecute and the next step if Action (on a Controller) processing the request is an async method? If so then why?

0reactions

ysmoradicommented, Jun 13, 2017

Remember that things have changed too in .NET Core. my approach is working fine on .NET Core 2 too