Open
Description
Summary
GenericHost is the preferred way of hosting apps and the WebHost is now legacy.
Obsoleting it would be a huge breaking change and to help customers to migrate from it we will need to also provide an analyzer.
This issue tracks the analyzer part of that effort.
People with more context
@Tratcher, @davidfowl, @halter73
Motivation and goals
Since GenericHost superseded WebHost in 3.0 we've stopped addressing issues in WebHost to minimize the maintenance burden, fixes only go into generic host. Long term we'll need to migrate people away from WebHost so we don't have to keep supporting two models.
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
ghost commentedon Nov 4, 2020
Thanks for contacting us.
We're moving this issue to the
Next sprint planningmilestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.ericsampson commentedon Nov 24, 2020
Would definitely be good to have an analyzer that helps guide the required changes that need to be made. Thanks!
BrennanConroy commentedon Jan 20, 2021
We aren't adding any new features to WebHost. Our templates have been using GenericHost since 3.0.
BrennanConroy commentedon Jan 20, 2021
Assigning to @Tratcher to drive the discussion and movement of this issue.
ghost commentedon Mar 30, 2021
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.
ghost commentedon Sep 13, 2022
Thanks for contacting us.
We're moving this issue to the
.NET 8 Planningmilestone 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.