While maintaining a multi-project solution in Visual Studio 2022, I encountered an unexpected and counterintuitive behavior: the NuGet Package Manager UI showed all packages as successfully updated, yet the .csproj files remained unchanged. No errors. No warnings. Everything seemed to have worked… but it hadn’t.
The issue occurs especially when multiple projects are selected in the solution and an attempt is made to update a shared package. The UI indicates a successful update, but the actual package versions remain the same. This can lead to confusion, build issues, or runtime problems caused by mismatched dependencies.
To raise awareness and help drive a fix, I submitted an official report on the Developer Community. You can read and upvote it here:
If you’ve experienced the same issue, I encourage you to join the conversation or confirm the behavior by clicking “I have the same question.” Engaging with the tools we use daily is essential to improving them. Even small feedback can make a big difference for the entire developer community, leading to more reliable and transparent tooling.
