Doug Bunting

Approved in email

Most 3.1.x CI builds don't use `darc`; the internal/release/5.0 branches (or similar for tooling) should be prioritized for a fix. @wtgodbe hacked dotnet-aspnetcore in https://dev.azure.com/dnceng/internal/_git/dotnet-aspnetcore/commit/279fd0871a89bdcdf9fda0c79bd63a7091b0d9e4?refName=refs%2Fheads%2Finternal%2Frelease%2F5.0&path=%2Feng%2Fcommon%2Fdarc-init.ps1&_a=contents to stick w/ an old...

@ajcvickers we've been taking Arcade updates in release/6.4 on a regular basis. I assume this also meets the maintenance bar because future Arcade updates won't run on CI w/o it❔...

Closing in favour of #2045

@marcpopMSFT @dsplaisted @jaredpar what's happening here and is there a workaround❔ Seeing the same issue w/ the 8.0.100-alpha.1.22478.15 SDK. The odd thing is our Microsoft.AspNetCore.Server.Kestrel.Core package uses `true` too but...

> Do the projects that are getting broken target .NET 7 or .NET 8? `net7.0`; we haven't made any TFM changes in main yet. (And won't until runtime changes their...

> My mental model would say it needs to be paired with a change like moving to a new target framework. According to , your mental model is upside down...

New news: `true` works. Didn't use it everywhere in my first attempt but that at least found other projects to change. I found a couple of projects (src\Servers\Kestrel\test\Interop.FunctionalTests\Interop.FunctionalTests.csproj and src\Servers\Kestrel\samples\Http3SampleApp\Http3SampleApp.csproj,...

@nagilson the requirement to use `true` when building for a non-default TFM is a mess and I have no understanding of why things work that way. Read the design document...

@wtgodbe changes to src/Components/test/E2ETest/Infrastructure/WebDriverExtensions/BasicTestAppAuthenticationWebDriverExtensions.cs are now in release/6.0. Feel free to label appropriately (some area, `tell-mode`) and merge if the version updates are useful.