Skip to content
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

apicompat --package-assembly-references is difficult to use #41686

Open
ericstj opened this issue Jun 19, 2024 · 1 comment
Open

apicompat --package-assembly-references is difficult to use #41686

ericstj opened this issue Jun 19, 2024 · 1 comment

Comments

@ericstj
Copy link
Member

ericstj commented Jun 19, 2024

The docs/usage say it should be TFM=file,file, but it's actually a tfm|file,file.

The docs don't indicate how to specify more than one TFM - but this is done by passing the parameter multiple times.

The docs say TFM but it actually needs the full form of the moniker. It should allow the short form (by parsing it).

The docs should also indicate that a directory works.

Alternate option for a package - generate a multi-targeting project for all frameworks discovered in package, add a reference to the package, restore it, and then drive API compat off such a project. This could save a lot of manual inputs, but it would be a lot to juggle (MSBuild reference, temporary project, etc etc).

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-NetSDK untriaged Request triage from a team member labels Jun 19, 2024
Copy link
Contributor

@dotnet/area-infrastructure-libraries a new issue has been filed in the ApiCompat area, please triage

@ViktorHofer ViktorHofer removed untriaged Request triage from a team member Area-NetSDK labels Mar 10, 2025
@ViktorHofer ViktorHofer added this to the Backlog milestone Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants