Skip to content

Conversation

@Kielek
Copy link
Contributor

@Kielek Kielek commented Dec 11, 2025

Fixes #1566

Add support for MSBuildTask for VS2026.

Now, there is no possibility to use 2026 without manually setting paths.

While reviewing, consider checking commit by commit. It brings explanations for the particular steps.

Needed for https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation

I confirm that the pull-request:

  • Follows the contribution guidelines
  • Is based on my own work
  • Is in compliance with my employer

…tion

It keeps old behavior for BuildTools
All new versions (2022+) for other editions will be taken from x64 folder.
…nstead of the year.

It might required adjustments when new versions of VS will be released
@Kielek Kielek changed the title Add support for MSBuildTask for VS2026. Add support for MSBuildTask for VS2026 Dec 11, 2025
@Kielek
Copy link
Contributor Author

Kielek commented Dec 11, 2025

quodana-scan is failing, due to following error:

2025/12/11 11:08:37 Starting from version 2023.2 release versions of Qodana Linters require connection to Qodana Cloud. 
To continue using Qodana, please ensure you have an access token and provide the token as the QODANA_TOKEN environment variable.
Obtain your token by registering at https://qodana.cloud/
For more details, please visit: https://www.jetbrains.com/help/qodana/cloud-quickstart.html
We also offer Community versions as an alternative. You can find them here: https://www.jetbrains.com/help/qodana/linters.html
✗  Qodana exited with code 1

@Kielek Kielek marked this pull request as ready for review December 12, 2025 09:27
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.

Could not find a suitable MSBuild instance - VS 2026

1 participant