Skip to content

Make release/10.0.1xx buildable locally on Windows - #7873

Merged
ViktorHofer merged 1 commit into
release/10.0.1xxfrom
MakeRelease10Buildable
Jul 21, 2026
Merged

ViktorHofer merged 1 commit into
release/10.0.1xxfrom
MakeRelease10Buildable

Conversation

@ViktorHofer

@ViktorHofer ViktorHofer commented Jul 21, 2026

Copy link
Copy Markdown
Member
  • Resolve issues when a matching SDK version is globally installed
  • Define an sdk::version entry in all global.json so that the host picks the correct SDK version (the one determined by the VMR root).
  • Use of TaskHostFactory in runtime to avoid file lock issues between the stage1 and stage2 build.

With that, everything except the vcxproj toolchain (wpf + aspnetcore) builds fine. Those two require VS2022 installed.

- Resolve issues when a matching SDK version is globally installed
- Define an sdk::version entry in all global.json so that the host
  picks the correct SDK version (the one determined by the VMR root).

With that, everything except the vcxproj toolchain (wpf + aspnetcore) builds fine.
Those two require VS2022 installed.
@ViktorHofer
ViktorHofer requested review from a team as code owners July 21, 2026 07:30
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

@dotnet-policy-service
dotnet-policy-service Bot requested review from a team July 21, 2026 07:31
@akoeplinger

Copy link
Copy Markdown
Member

FYI nuget.client recently removed the sdk entry from their global.json: NuGet/NuGet.Client#7182

Comment thread src/runtime/eng/testing/tests.targets
@ViktorHofer

Copy link
Copy Markdown
Member Author

FYI nuget.client recently removed the sdk entry from their global.json: NuGet/NuGet.Client#7182

Doesn't matter for 1xx as they still have it there. I will need to fight the battle for 10.0.3xx onwards with them though. I prefer adding the entry to each repo over forcing the VMR to always add it as it's in general the right thing to do. But I might need to special case the VMR yet again for nuget-client. EricStj and I let them know multiple times that the sdk::version entry is essential. Otherwise you would run into these exact kind of issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants