One of the repos that's failing to build for Unified Build is aspnetcore with the following error:

D:\a\_work\1\vmr\.dotnet\sdk\10.0.100-alpha.1.25056.8\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(266,5): error NETSDK1060: Error reading assets file: Error loading lock file 'D:\a\_work\1\vmr\src\aspnetcore\artifacts\obj\RepoTasks\project.assets.json' : Could not load file or assembly 'System.Text.Json, Version=8.0.0.5, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified. [D:\a\_work\1\vmr\src\aspnetcore\eng\tools\RepoTasks\RepoTasks.csproj]

This only fails on Windows legs (it's not related to source build).

Here's a binlog: aspnetcore.Build.repotasks.zip

And a build link.

It's not clear to me what the cause of this is. Pinging @wtgodbe

D:\a_work\1\vmr.dotnet\sdk\10.0.100-alpha.1.25056.8\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(266,5): error NETSDK1060: Error reading assets file: Error loading lock file 'D:\a_work\1\vmr\src\aspnetcore\artifacts\obj\RepoTasks\project.assets.json' : Could not load file or assembly 'System.Text.Json, Version=8.0.0.5, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified. [D:\a_work\1\vmr\src\aspnetcore\eng\tools\RepoTasks\RepoTasks.csproj]

@rainersigwald you might have an idea. This happens when building aspnetcore with desktop msbuild, the first time that NuGet assemblies are loaded. NuGet references STJ/8.0.0.5 and msbuild.exe 17.12.3+4ae11fa8e is being used.

D:\a_work\1\vmr.dotnet\sdk\10.0.100-alpha.1.25056.8\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(266,5): error NETSDK1060: Error reading assets file: Error loading lock file 'D:\a_work\1\vmr\src\aspnetcore\artifacts\obj\RepoTasks\project.assets.json' : Could not load file or assembly 'System.Text.Json, Version=8.0.0.5, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified. [D:\a_work\1\vmr\src\aspnetcore\eng\tools\RepoTasks\RepoTasks.csproj]

@rainersigwald you might have an idea. This happens when building aspnetcore with desktop msbuild, the first time that NuGet assemblies are loaded. NuGet references STJ/8.0.0.5 and msbuild.exe 17.12.3+4ae11fa8e is being used.

Could it be related to this change: dotnet/msbuild#11124

Could it be related to this change: dotnet/msbuild#11124

This went into the vs17.10 branch. CI uses VS 17.12 / msbuild 17.12.3 (dotnet/msbuild@4ae11fa as its HEAD). That one is unfortunately missing dotnet/msbuild@eacead3 which is required for STJ/8.0.0.5.

I think this change caused the mismatch: NuGet/NuGet.Client@8791d42

cc @zivkan @marcpopMSFT

That makes sense but GA 17.12 should have always had 8.0.0.5. However from the binlog:

Assembly loaded during Evaluation: System.Text.Json, Version=8.0.0.4, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (location: C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\System.Text.Json.dll, MVID: d267e778-f3b7-48d4-a754-4adb2eeb2095, AppDomain: [Default])

That Preview makes me wonder if this is an old preview before that change? Do we know the exact VS version on the machine?

I think that the NuGet team's decision to update to STJ/8.0.0.5 was correct at that time. Our build images are just lagging behind way too much. The windows.vs2022preview.amd64.open image has a 3-months old version of msbuild installed.

According to https://dev.azure.com/dnceng/internal/_wiki/wikis/DNCEng%20Services%20Wiki/899/VS2022-Upgrade-Schedule, windows.vs2022preview.amd64.open should have VS 17.13.0 Preview 1 installed but https://helix.dot.net/ mentions Preview 17.12.0-pre.4 and CI shows that the installed VS version is definitely not 17.13.0 Preview 1. @ilyas1974 @mmitche

Fortunately, the image should get updated today.

I think that the NuGet team's decision to update to STJ/8.0.0.5 was correct at that time.

Agreed, I believe it went into their 17.13 branch so "assume GA 17.12" feels fine to me.

@ViktorHofer - Now we're getting this for aspnetcore:

Unable to find directory for jdk 11.0.24%3B please make sure the tool is installed on this image.

This affects all VMR builds right now. See #45822