Reputation: 477
I have the application (solution in VS2010) with +-10 projects. Some of these projects are quite large (dozens of folders and hundreds of files).
When I make a change in project on lower level and I want to run my tests (+-10 seconds) then I have to wait 2 minutes for projects build. This is very inefficient.
Is there any way to speed-up build? For example, split current projects into multiple projects or something else?
Or are there some general advice and recommendations to speed-up building projects in Visual Studio?
Upvotes: 4
Views: 1504
Reputation: 759
Try this: Go to "Tools" menu -> "Options" -> "Projects And Solutions" -> "Build And Run" And increase the value of "Maximum number of parallel project builds" to 32 or greater.
Upvotes: 3
Reputation: 12629
In my experience solutions with large number of projects build slowly on vs2010 and there is not much you can do about it:
Bin\Debug Bin\Release
folder so that new dlls are loaded on application start. This is requited because if you don't build project its dependencies wont be copied to its output directory.Upvotes: 1
Reputation: 2817
Try to use tools that allow concurrent test execution coupled with shadow building - NCrunch or MightyMoose. Also try to get rid of unused references - for example move all tests that test only your core project to separate project so that they get executed right after core is built. Try not to use MS accessors, because they force to fully recompile all projects that they are referencing. And of course use SSD disks.
Upvotes: 1