William Godbe

Opened https://github.com/dotnet/aspnetcore/pull/41137 to try to see if CI failures are due to a reference resolution problem, or a new functional change the tests are now picking up

Ping @halter73 and @HaoK on https://github.com/dotnet/aspnetcore/pull/40885#issuecomment-1092243041 - this isn't manifesting like a reference resolution error, so I'm thinking that these tests are picking up a behavioral change that they weren't...

``` Log Critical[0]: Unable to start Kestrel. System.InvalidOperationException: Dynamic port binding is not supported when binding to localhost. You must either bind to 127.0.0.1:0 or [::1]:0, or both. at Microsoft.AspNetCore.Server.Kestrel.Core.LocalhostListenOptions..ctor(Int32...

The build output shows those kestrel failures are happening for (at least) `Libuv.BindTests` and `Sockets.BindTests` but I don't see those in the test tab - not sure why not. I...

Actually, I see the same Kestrel failures in a recent green CI run of 2.1, so that looks like a red herring. The Identity failures appear real though, and are...

The failures started on this PR, likely since we're changing `UseProjectReferences` to be globally `true` to satisfy component governance - my theory is that's leading tests to pick up new...

@TanayParikh could you take a look at the failures here since they appear to be related to Razor?

Here's a failing build: https://dnceng.visualstudio.com/internal/_build/results?buildId=399756 We can put up PRs for this now if the fix is known, but please don't merge into 3.1 yet, as that branch is locked...

SDL is still disabled in 3.1 - I can look into fixing up the Area Path tomorrow morning, but we'll have to wait on merging the fix until the branches...

/backport to release/7.0