Fix MSBuild tool resolve for VS2026 - #420
Merged
ChrisonSimtian merged 2 commits intoJun 25, 2026
Merged
Conversation
Kielek
approved these changes
Jun 24, 2026
Kielek
left a comment
Kielek
left a comment
There was a problem hiding this comment.
LGTM. Great to see the fix propagated here.
If nothing change, I will need to switch https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation to new tool.
ChrisonSimtian
added
the
Can Merge
ChrisonSimtian
force-pushed
the
fix/vs2026-msbuild-resolve
branch
from
June 25, 2026 00:26
5182de0 to
e55ae28
Compare
This was referenced Aug 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This originates from: nuke-build/nuke#1583
Thanks @Kielek