Skip to content

Limit the expected search location for the dotnet muxer from the sdk resolver result #49824

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

Merged
merged 2 commits into from
Jul 18, 2025

Conversation

baronfel
Copy link
Member

@baronfel baronfel commented Jul 16, 2025

We limit the probing to the expected layouts instead of allowing unrestricted probing up the file system.

Also part of #49363

@Copilot Copilot AI review requested due to automatic review settings July 16, 2025 22:01
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR changes the SDK resolver to use a more restrictive approach for locating the dotnet muxer binary. Instead of probing up the file system hierarchy, it now assumes the standard SDK layout where the muxer is exactly two directories above the SDK directory.

  • Replaces upward directory traversal with direct path calculation based on expected SDK layout
  • Renames method and variables to better reflect the muxer-specific functionality
  • Improves documentation to explain the expected relationship between SDK and muxer locations

@baronfel baronfel enabled auto-merge (squash) July 16, 2025 22:43
@baronfel baronfel force-pushed the limit-dotnet-muxer-search-scope branch from 4ec8454 to 6326120 Compare July 17, 2025 23:07
@baronfel baronfel merged commit e761e9c into dotnet:main Jul 18, 2025
27 checks passed
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