Use Muxer from .NET SDK for dotnet discovery#4732
Merged
liliankasem merged 8 commits intomainfrom Nov 18, 2025
Merged
Conversation
jviau
reviewed
Nov 17, 2025
jviau
reviewed
Nov 17, 2025
liliankasem
force-pushed
the
liliankasem/use-dotnet-muxer-from-dotnetcli
branch
from
94bfefc to
48de81b
Compare
jviau
approved these changes
Nov 17, 2025
aishwaryabh
approved these changes
Nov 18, 2025
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
4 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.
Issue describing the changes in this PR
resolves #4725, #3285
Pull request checklist
release_notes.mdAdditional information
Replace CommandChecker.CommandExists with DotnetMuxer class copied from the .NET SDK to improve dotnet installation discovery. This provides more comprehensive detection using multiple fallback strategies including DOTNET_HOST_PATH, DOTNET_ROOT, and process path resolution.
Changes: