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

Turning off .NET Package Validation check for backwards compatibility across different frameworks feature #40847

Open
vsfeedback opened this issue May 13, 2024 · 2 comments
Labels
Area-ApiCompat untriaged Request triage from a team member

Comments

@vsfeedback
Copy link

This issue has been moved from a ticket on Developer Community.


I am trying to adopt .NET package validation https://learn.microsoft.com/en-us/dotnet/fundamentals/apicompat/package-validation/overview as a replacement for our current solution to a set of libraries that my team maintains however, upon enabling it through true we get errors due to backwards compatibility between our different target frameworks which are intentional. We do not offer the same features depending on what framework our users run on.

For example, we might have an interface that we support for users running on NET462 that we do not intend to have implemented for a user running on NET6. Is there a property or on-going work that will allow us to turn off package validation checks for framework compatibility?

Our repo supports the following frameworks:

net462;net472;netstandard2.0;net6.0;net7.0;net8.0

Original Comments

Feedback Bot on 12/19/2023, 03:27 AM:

(private comment, text removed)

Feedback Bot on 4/2/2024, 07:34 AM:

(private comment, text removed)


Original Solutions

(no solutions)

@dotnet-policy-service dotnet-policy-service bot added the untriaged Request triage from a team member label May 13, 2024
@ViktorHofer ViktorHofer transferred this issue from dotnet/runtime May 13, 2024
Copy link
Contributor

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

@ViktorHofer
Copy link
Member

PackageValidation offers the following validators:

It sounds like you only want to use the baseline package validation feature and disable the other validators. That isn't supported today but if requested, can be implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-ApiCompat untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

2 participants