Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade MSBuildLocator to 1.6.1 #69769

Merged

Conversation

jasonmalinowski
Copy link
Member

@jasonmalinowski jasonmalinowski commented Aug 30, 2023

This version should better discover MSBuild on some Mac machines that have .NET installed by Homebrew.

Fixes dotnet/vscode-csharp#6063
Fixes dotnet/vscode-csharp#6253
Fixes dotnet/vscode-csharp#6122
Fixes dotnet/vscode-csharp#6198

This version should better discover MSBuild on some Mac machines
that have .NET installed by Homebrew.
@jasonmalinowski jasonmalinowski requested a review from a team as a code owner August 30, 2023 21:52
@jasonmalinowski jasonmalinowski self-assigned this Aug 30, 2023
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Aug 30, 2023
@dibarbet
Copy link
Member

I think this also fixes
dotnet/vscode-csharp#6122
and
dotnet/vscode-csharp#6198

@jasonmalinowski
Copy link
Member Author

@dibarbet Ah right, I thought there was more.

@jasonmalinowski jasonmalinowski merged commit 9ec628f into dotnet:main Aug 30, 2023
25 of 27 checks passed
@jasonmalinowski jasonmalinowski deleted the upgrade-msbuild-locator branch August 30, 2023 23:43
@ghost ghost added this to the Next milestone Aug 30, 2023
@mthalman
Copy link
Member

mthalman commented Sep 7, 2023

This change requires the MSBuildLocator submodule to be updated in source-build-externals. @jasonmalinowski, could you take care of that please? Instructions for doing that are here. Source-build is currently building version 1.5.5 of MSBuildLocator. So updating the referenced version to 1.6.1 here is causing prebuilts to be introduced, as mentioned in #69847.

@jasonmalinowski
Copy link
Member Author

@mthalman I'm following up with the repository owners to figure out who should do it.

@rainersigwald
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
6 participants