So I am quit confused. I have just installed the source code and got all that working but catch my supersize that using run without debugging compiles and runs code faster than just building it. This is a difference of a few seconds and minutes. I assume it has something to do with the build configuration? I have already disable my obvious things from the giant list of things selected but it doesn’t seem to help at all.
Any pointers would be wonderful
Yep.
That’s how the world goes around 
You should not be surprised. Running a big project in debug takes much, much more time to run. Also it runs significantly slower than a per-compiled binary file. The debug files are also much larger.
All this is done to allow you to “watch” variables pause and break execution, change values at run-time and much more. It also loads a bunch of debugging tools and hooks them to your project like profiler programs and resource watchers.
The only way around this is to have pre-build binaries to work with… And it’s still much slower.
wow. I didn’t think someone could answer this question incorrectly, but congratulations! you did it. Since you didn’t even read the title let me rephrase the question for you. Running without debugging i.e using ctrl-f5 builds and runs the project in seconds, however just building the project ctrl-shift-b takes a very long time. I have just started working with the source code and not just the c++ project and its only doing it when I am running from source.
ctrl shift b - build solution
ctrl f5 - builds only the project
single solution may have multiple projects,
more code to compile takes more time
PS. Don’t be so rude…
Aaah, I don’t know why I didn’t think of that thanks. I thought it would just build the default project not the whole thing.
PS. I can be as rude as I choose.