-
Notifications
You must be signed in to change notification settings - Fork 249
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
Consider removing the extensibility that allows other package managers to be shown as compatible #6623
Comments
Another customer filled a similar issue to this one: |
Or you should consider that in some cases we need to be able to modify the content that would be distributed by the package into our project to address issues with it or for any other reason. Its frustrating to be held hostage to a bug that you can correct, but are artificially forbidden from doing so. Tools should enable, not restrict. |
//cc @rrelyea Basically I can't make this method async. We should retriage it again. |
Related (now closed) bug I filed dotnet/aspnetcore#27480 |
Create any PR/PJ based project and open the PM UI and see that there's a
when we list those packages.
This is achieved with an extensibility point that allows other "alternative" managers to talk to NuGet and advertise if they're the preferred option for those packages.
Code here.
The reason why these packages are incompatible is because they contain content, the mutable v2 kind.
However, if you read the ASP.NET docs, there's conflicting information.
These 2 packages are perfect examples of what contentFiles should be used for.
We should consider removing this "AlternativePackageManagerProviders" goo, and work with the jquery/bootstrap nuget package maintainers to make these 2 packages PR compatible.
The text was updated successfully, but these errors were encountered: