   [.net] Incredibuild in c# project
  Hi allIn the past, I made excellent experiance with Xoreax IncrediBuild. However This was with native CPlusPlus projects... meanwhile I found it being also very usefull with managed CPlusPlus targets. Unfortunatly -skip explanation of circumstances- I was not able to test its benefit in a realworld, large scale c# project.Does anybody of you use Incredibuild with c#?If so - what is your experience with it?When observing c# builds, my perception is, that MSVS spends pretty much time to figure out dependencies - compared to the time it actually takes to build the targets. So naturally the benefit would be limited to the already fast compilation part.What's your perception?Best Jochen   
  There should be no reason to need Incredibuild for a C#.  I have yet to see a C# project that would have any need for it.C# projects don't have the same issues that C/C++ projects with interdependence and header files.  theTroll   ;Quote:Original post by jochenWhen observing c# builds, my perception is, that MSVS spends pretty much time to figure out dependencies - compared to the time it actually takes to build the targets. So naturally the benefit would be limited to the already fast compilation part.Just curious: what triggered you into thinking that a lot of time is being spend on figuring out dependencies?;  well, I'm working on a project that has more than 100 assemblies. And buildtime has definitly become significant.When I built a MSVC solution with about 50 Assemblies, the output window shows:updating dependencies...for like a minute.BestJochen   ;  Are they all in the same solution?At work, we have around 130 projects, but they're broken up into many solutions (usually about 5-6 projects per solution, it depends on how things are structured) and our build time is around 5 minutes for a full rebuild.Keeping the number of projects small also keep memory usage of Visual Studio down, which is a plus :-)   ;  well long story short, unfortunately I really need this lot of assemblies. The dependency tree is quite big.Quote:There should be no reason to need Incredibuild for a C#. I have yet to see a C# project that would have any need for it.Well, unfortunatly this project's buildtime is more than 1h, even when rebuilding only a part of it. :-(   ;  But all in the same solution? We have around the same number of projects as you, but split up over many solutions. Our build script is set up to build the solutions in the correct order so that dependencies are correct.I would also suggest you perhaps look into using msbuild directly, rather than building from Visual Studio.Especially if you use something like ReSharper, I can't imagine how you can be productive with that many projects in a single solution....   