Debug and Build VS Run and Compile?

Joined
11/14/15
Messages
50
Points
18
Hi, I used to use Dev-C++ environment instead of VC, and in Dev, we have three options:
a. Compile.
b. Run. To run, we must have complied before.
c. Compile and run.
And now, in VC, we have start debugging, start without debugging and build and rebuild. I want to figure out the correspondence between these two set of terminology. Is build in VC means the same as Compile, and what's the difference between build and rebuild?
What's more, does start debugging means compile and run? And what's the difference between start debugging and start without debugging?
What if we have compiled already and just want it to run again? Which one should we choose?
It may sound like a stupid question but I still cannot understand it thoroughly.
Thank you very much.
 
Build=Compile+Link

Build all ensures everything gets rebuilt whereas build will only recompile files which have changed.

Start with debugging allows you to use the VS debugger
 
So VC environment is a compile-and-go system where I cannot just store the compiling result( I used to think after compiling or buildeing, my code turns into a binary format such as 010001110 which can be recognizes by the computer instead of myself) in the primary memory so that next time I can re-
Build=Compile+Link

Build all ensures everything gets rebuilt whereas build will only recompile files which have changed.

Start with debugging allows you to use the VS debugger
I see. And what's the difference between start debugging and start without debugging?
excute the same code without building it? I have these choices and what's the difference between build solution and build HW 7.1?
Thank you~
 

Attachments

  • 3.webp
    3.webp
    14.7 KB · Views: 33
Start with debugging allows you to use the VS debugger. Without does not.

A solution can technically have multiple projects. Build solution builds them all.
 
Back
Top Bottom