Click here to Skip to main content
14,297,259 members
Rate this:
Please Sign up or sign in to vote.
See more:
I need to know what is the most efficient way to compile and run with VS. Hundreds of times a day I have to click on compile Debug, Compile Release and "Start" and wait to get back to the line where I work. There's no other way?

At a minimum, there could be a button that compiles in debug, compiles in Release, and executes. I do not get it.

As for the Debug in which you can go back, modify and continue, as far as I know does not exist, it only allows you to see the value that the unmodified variable had. Do I do it wrong or is that so?

What I have tried:

in all the sites of all the sites of internet
Updated 2 days ago
Rate this:
Please Sign up or sign in to vote.

Solution 1


That's it. Compiles, builds, runs in the debugger if it compiles OK.
Richard Deeming yesterday
F10 is also useful - when you're not debugging, it compiles, starts the application, and breaks on the first line of user code. :)
Rate this:
Please Sign up or sign in to vote.

Solution 3

You do not have to compile Debug + Release each time. In fact, while debugging, it makes sense to only deal with the debug version. Ideally, you should only compile the release version once it has been toroughly debugged, or if you want to do a benchmark test of release version against debug version, for example.

But you definitively do not need to compile both versions each time you want to launch the debugger.
zequion 2 days ago
Right now I have compiled in Debug but not in Release and when pressing F11 on a certain line I get this message:

The source code file is different since the module was generated. Do you want the debugger to use it anyway?

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100