Review if UseRouting should still be explicitly called in the project templates

[danroth27]

Is the explicit call to UseRouting in the ASP.NET Core project templates still required? It looks like it was originally introduced to workaround #34146 which has since been resolved.

@DamianEdwards @davidfowl

[DamianEdwards]

My understanding is it's not required, it's just more explicit. I'm supportive of removing it unless we have compelling reasons not to.

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.

[captainsafia]

We learned the hard way this release that having UseRouting explicitly in the template is a helpful indicator for figuring out what middlewares should go before endpoint routing vs. after. Given that, I think it's helpful to keep it in the template as a line of delineation where users know to put additional customizations.

[danroth27]

We learned the hard way this release that having UseRouting explicitly in the template is a helpful indicator for figuring out what middlewares should go before endpoint routing vs. after. Given that, I think it's helpful to keep it in the template as a line of delineation where users know to put additional customizations.

@captainsafia Which middleware need to go before endpoint routing? And do we have that documented anywhere? It just seems strange that we set up the routing middleware in the host builder by default, but then we've decided that you really actually need to explicitly set it up.

[captainsafia]

Which middleware need to go before endpoint routing?

Static file serving, HTTPS redirect, status code pages are the first ones that come to mind. That's documented here.

It just seems strange that we set up the routing middleware in the host builder by default, but then we've decided that you really actually need to explicitly set it up.

Yes, it is strange. This decision is in reaction to the bug reports we've gotten over the past year that relate to the implicitly-on behavior. There are some scenarios where it sends users into a bit of failure and we opted to avoid removing the explicit addition from the template until we figured those out.

[danroth27]

Adding @mkArtakMSFT and @javiercn.

@captainsafia Is the conclusion here then that we should add an explicit call to UseRouting to the Blazor templates as well?

[captainsafia]

@captainsafia Is the conclusion here then that we should add an explicit call to UseRouting to the Blazor templates as well?

I'm biased towards leaving the Blazor templates as-is. Hopefully, we'll resolve the implicit middleware issue once and for-all for .NET 9. If not, we can revisit unifying the way the minimal host is setup for all templates later.