Please also see Enhance VS Extension (Proposal 1) and Enhance VS
Extension (Proposal 2).
Issue: When you have a series of NuGets which are each dependent on each other, rebuilding them automatically when a change is made to a base NuGet is really, really painful and requires lots of PowerShell script writing, etc. that
makes it beyond the pain threshold of most devs.
Proposal: Add a "Publish Manager" dialog via the VS Extensions with a menu item to access it from the Tools menu of VS.
This dialog would allow a top level directory to be specified, below which it will scan for solutions & projects that have publish settings for NuGets (or have associated NuSpec files).
It will then create a dependency tree of projects, showing which projects are dependent on NuGets created by other projects within the file structure, it will also keep track of which projects are 'out of date' etc.
Right clicking on projects will open the following context menu:
These will also be available from a toolbar.
For now this system will be limited to monitoring source code on your file system, which means that dependent NuGets will all have to be 'checked out' to local working copies.
Please Note: I have already implemented the vast majority of this code (without publish settings support) as part of a very fast and efficient class library that I use from a PowerShell library to calculate NuGet dependencies using
a topological sort algorithm, so I would be happy to take it to the next step if there is a likelihood of a pull request being accepted.
Regardless, it should be possible for a lot of the functionality to be available from the NuGet command line using a shared class library - which would be useful for CI servers. I wouldn't embed in the command line as the command line wouldn't easily
support folder wathcing with realtime updating which is possible (and desirous) for this functionality.