spot process separation studio 4 pre release

This speeds up your build by using the output of the last build of these projects, from wherever they dump their binaries to. Solution -> Right Click -> Configuration Manager -> uncheck Build on any projects that don't change and aren't needed every build for some other reason. Something else you can do is edit the build definition and remove any unmodified projects (depending on how you links are.you know what's needed/updated/not needed). It keeps a lot of stuff out of VS memory. (pun not intended)Īnother approach you may want to consider is to just unload the projects you are not using, just right click and unload the ones you're not working on.this should result in a much snappier Visual Studio. Once that build is complete, I could open my A/D-solution and edit/build only those 2 projects.īut I fear there is no elegant solution for my problem. But that would only work if I could have an intact 'complete' solution containing A,B,C and D if I want to build all projects from scratch. (Obviously, the interface of A that is used by B must remain unchanged for that.) Then I would like to have A and D in one solution, B and C in another. For example, imagine I have the dependency chain A is referenced by B is referenced by C is referenced by DĪnd imagine that A and D are often modified together but B and C rarely change. But that grouping does not always match the dependencies. I would like to have the projects that are usually modified together in one solution). in a batch file) seems error-prone to me.Īlso I would like to group the projects 'logically' (i.e. Maintaining the build order for 8 separate solutions by hand (e.g. That's why I would like to keep the 'full' solution where VS can figure out the correct build order for a full build.

So splitting it into 2 parts isn't really what I had in mind, I was more thinking about 5-8 parts. I'd like to clarify my question a bit: My solution contains 44 projects, not including tests. But if I do that, my 'full' solution doesn't work any more, because the dependencies are lost. I can add the references as 'normal' file references. But if I do that, VS can't find the project references any more (because they're not in the same solution). My first idea was to create new empty solutions and add some of the existing project files into each of these solutions. Otherwise, splitting projects into solutions is trivial, of course.) I would also like to keep the 'full' solution with all projects (it's handy for for automated builds or for big refactoring actions that affect all projects). So I decided to split the solution into multiple solutions that contain 3-5 projects. Working with that solution is quite slow, and usually I only need a few projects at a time.

I have a Visual Studio 2008 solution with >40 C# and C++/CLI projects that depend on each other.

Spot process separation studio 4 pre release