ReferenceSwitcher as a tool to facilitate partitioned solutions

[konste]

I'm looking to split huge VS solution to multiple smaller "partial" solutions. Partial solutions would build separate components (in a form of one or multiple NuGet packages) and Master solution would assemble them together. Partial solutions also tend to reference projects from other partial solutions. Normally developers only load one partial solution they work on and expect all other components to be available as NuGets to accelerate local dev build. But occasionally developers are interested to load more than one code area and have some NuGets in their partial solution replaced with the references to the actual projects.

Your reference switcher is the closest thing I could find to make it happen, but it misses a couple important usability points.

1. We use more than hundred external NuGet packages, which we never going to switch to project references. Would be great to exclude those from UI based on some criteria or simple configuration file.
2. When NuGet get replaced with project references it usually means that the whole another partial solution is switched, so instead of NuGet by NuGet control it would be much more effective to switch those replacements on and off for some logical GROUPS of NuGet packages, again probably taken from configuration.

Does it makes sense?

Thank you! Konstantin

[RicoSuter]

Hi Konstantin, Your suggestions make sense for bigger projects. Currently I dont have enough time to implement all these features - first I'd like to make the current features stable... Feel free to fork the project and add these features... Rico