Skip to content
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

Closed
pranavkm opened this issue Feb 2, 2022 · 8 comments
Closed

Provide documentation to use Owin correctly with ASP.NET Core #39943

pranavkm opened this issue Feb 2, 2022 · 8 comments
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions Docs This issue tracks updating documentation
Milestone

Comments

@pranavkm
Copy link
Contributor

pranavkm commented Feb 2, 2022

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 using IApplicationLifetime.ApplicationStopping.

This glue code is required to robustly run a existing Katana-based app on ASP.NET Core. This issue tracks this work.

@rafikiassumani-msft rafikiassumani-msft added the Docs This issue tracks updating documentation label Feb 2, 2022
@rafikiassumani-msft rafikiassumani-msft added this to the .NET 7 Planning milestone Feb 2, 2022
@ghost
Copy link

ghost commented Feb 2, 2022

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@adityamandaleeka
Copy link
Member

@Tratcher I'll let you decide how/when this should be addressed.

@Tratcher Tratcher modified the milestones: .NET 7 Planning, Backlog Aug 23, 2022
@ghost
Copy link

ghost commented Aug 23, 2022

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.

@Tratcher
Copy link
Member

Backlogging due to very low demand. We'll cover some of this with the System.Web interop work.

@davidfowl
Copy link
Member

@Tratcher instead of backlogging this can we associate it with the migration work? This is too trivial to backlog

@Tratcher
Copy link
Member

@davidfowl
Copy link
Member

Sounds good to me.

@Tratcher
Copy link
Member

Moved to dotnet/systemweb-adapters#161

@ghost ghost locked as resolved and limited conversation to collaborators Sep 22, 2022
@amcasey amcasey added area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions and removed area-runtime labels Aug 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions Docs This issue tracks updating documentation
Projects
None yet
Development

No branches or pull requests

6 participants