I have been considering building my solution – consisting of .NET- and C++-projects – with the devenv.com via command line. My hopes were that – since an unopened Visual Studio IDE produces no unnecessary overhead – the build would complete much faster, but this was not the case in my attempts.

This is the command I was using to achieve this:

devenv.com "{PathToMySolution}" /Rebuild Debug

By executing this, I receive a correct build of the solution; however, it takes more than twice as long to get the result compared to the IDE.

Am I missing some massive overhead that is solely produced with devenv.com? (and is there a meaningful way to bypass it?)