I currently have NuGet Package Restore enabled and I'm using "repositoryPath" to store the packages for all the projects on my development machine in a single location.
NuGet Package Manager does not appear to be designed to handle this scenario properly.
When attempting to "Manage NuGet Packages for Solution", the installed packages list contains all the packages in my Packages folder, not just the packages that are currently being used by the projects in my solution. This causes various problems, such as packages that need updating not showing up in the Updates list.
If I attempt to manage packages at the project level (rather than for the whole solution), I also get strange behavior where sometimes no items appear in the Update list even though I know updates are available.
Comments: Same issue as WayneBrantley here. Packages that are no longer used remain available in the "Updates" tab, and it's impossible to update the package for any project.
NuGet Package Manager does not appear to be designed to handle this scenario properly.
When attempting to "Manage NuGet Packages for Solution", the installed packages list contains all the packages in my Packages folder, not just the packages that are currently being used by the projects in my solution. This causes various problems, such as packages that need updating not showing up in the Updates list.
If I attempt to manage packages at the project level (rather than for the whole solution), I also get strange behavior where sometimes no items appear in the Update list even though I know updates are available.
Comments: Same issue as WayneBrantley here. Packages that are no longer used remain available in the "Updates" tab, and it's impossible to update the package for any project.