You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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.
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.0Original 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)
The text was updated successfully, but these errors were encountered: