-
Notifications
You must be signed in to change notification settings - Fork 258
[Feature]: Add support for central package management to Visual Studio Package Manager UI for legacy projects #9521
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
Comments
Is this not yet implemented? For legacy projects the VS Package Manager UI adds (I know that this issue is still open. But I'm asking because the related issue #9018 is also still open, but works in VS.) |
When you have mixed projects in your solution, this now breaks the CPM: the Directory.Packages.props is updated AND the legacy projects are polluted with the |
I also experience the same behavior (in a solution which contains legacy projects (non-SDK-style) only). Reading the documentation, one might come to the conclusion that all this should already work:
|
Would really like to see this. |
Upgraded my projects to .NET 8 - but still seeing these problems. |
In addition to the package install/update issue, I notice that the Properties window does not display anything for Package References added via central package management. For other references, I get info about the version, source path, etc... |
Details about Problem
Implement the back-end changes to support Visual Studio update scenarios for non-sdk projects.
The text was updated successfully, but these errors were encountered: