-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Open
Labels
Priority:1Work that is critical for the release, but we could probably ship withoutWork that is critical for the release, but we could probably ship withoutarea-mvcIncludes: MVC, Actions and Controllers, Localization, CORS, most templatesIncludes: MVC, Actions and Controllers, Localization, CORS, most templatesenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing onefeature-routing
Milestone
Description
Hi,
i've just tested the scenario described in this old issue on dotnet 5.0 but it still not working.
#20489
I guess that that feature was not included in the 5.0 planning and unfortunately it's blocking the upgrade of a lot of software due to the regression occurred when switching to the new Routing mechanism in dotnetcore 3.0.
What is the solution to allow ambient parameter to flow between areas for dotnet 5.0 and 6.0 ?
Thanks
ajbeaven, Muchiachio, fschmied, WGroenestein, valeriob and 3 more
Metadata
Metadata
Assignees
Labels
Priority:1Work that is critical for the release, but we could probably ship withoutWork that is critical for the release, but we could probably ship withoutarea-mvcIncludes: MVC, Actions and Controllers, Localization, CORS, most templatesIncludes: MVC, Actions and Controllers, Localization, CORS, most templatesenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing onefeature-routing