-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide documentation to use Owin correctly with ASP.NET Core #39943
Comments
Thanks for contacting us. We're moving this issue to the |
@Tratcher I'll let you decide how/when this should be addressed. |
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
Backlogging due to very low demand. We'll cover some of this with the System.Web interop work. |
@Tratcher instead of backlogging this can we associate it with the migration work? This is too trivial to backlog |
How about moving it to https://github.com/dotnet/systemweb-adapters/issues? |
Sounds good to me. |
Moved to dotnet/systemweb-adapters#161 |
ASP.NET Core's current owin documentation does not details on adding the glue code to plug in things like logging, data protection, hosting shutdown tokens etc. For instance, https://www.codeproject.com/Articles/1122162/Implement-Owin-Pipeline-using-Asp-net-Core has a section about configuring the
OnAppDisposing
token usingIApplicationLifetime.ApplicationStopping
.This glue code is required to robustly run a existing Katana-based app on ASP.NET Core. This issue tracks this work.
The text was updated successfully, but these errors were encountered: