Skip to content

The SDK should provide a RID-negotiation Task for other tools to use #48352

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

Open
baronfel opened this issue Apr 10, 2025 · 0 comments
Open

The SDK should provide a RID-negotiation Task for other tools to use #48352

baronfel opened this issue Apr 10, 2025 · 0 comments
Assignees
Labels
Area-NetSDK untriaged Request triage from a team member

Comments

@baronfel
Copy link
Member

Is your feature request related to a problem? Please describe.

There are now two examples of partner teams needing to perform RID-negotiation as part of their normal order of business

  • containers use RID-negotiation to map from multi-arch container synthetic RIDs to find the best match for the .NET RID being targeted
  • Aspire uses RID-negotiation to influence which implicit PackageReferences to add on Restore

Describe the solution you'd like

In both cases the core logic is very simple:

  • using a given RID graph path
  • and a set of 'supported RIDs'
  • and a single 'target RID'
  • return the 'supported RID' that is the 'best fit' for the 'target RID'

If we shipped this in-box we'd simplify the needs of partner teams and provide a way to surface more 'hidden' data that the SDK already knows about.

@ghost ghost added the untriaged Request triage from a team member label Apr 10, 2025
@baronfel baronfel self-assigned this Apr 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-NetSDK untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

1 participant