AR-May

@JaynieBai could you please check whether it is shell or msbuild parsing causing this error? For that, please check which parameters msbuild received. You can set `$env:MSBUILDDEBUGONSTART=1`, run the build,...

Team triage: What version of the dotnet sdk are you using (you can use `dotnet --version` to see the version)?

@JaynieBai can you please take a look at this, try to repro/investigate this?

I see no more binskim warnings in Ci

Discussed the issue internally. Problem: The build results cache was not initially intended to be used cross MSBuild versions (i.e. to be produced by one version and used by another)....

Have been able to reproduce the issue: 1. Create a vcxproj console project from a VS template 2. Open a cmd and set `MSBUILDLOGIMPORTS` and `MSBUILDDEBUGENGINE` environment variables. 3. Open...

@skyslide22 It seems like there might be some issue with incrementality in your builds. Let's try first to verify that the rebuild works without issues. Could you please instead of...

@baronfel yes, we would need the blazor team to provide us with a [binary log](https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Providing-Binary-Logs.md) of the bad deployment.

Team triage: > Is that the recommended way? Yes, we recommend enabling Long Paths on the OS to fix this. As part of this issue, we should consider updating the...

> If there are multiple options, it will throw; if there is only one, it will execute it after tweaking all the _ to have the right type. I am...