VS compilation crisis

Question

0.00/5 (No votes)

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 internet.in all the sites of internet

Posted 11-Sep-19 18:08pm

zequion

Updated 11-Sep-19 22:36pm

v2

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

OriginalGriff · Answer 1 · 2019-09-11T19:59:00

Solution 1

F5

That's it. Compiles, builds, runs in the debugger if it compiles OK.

Posted 11-Sep-19 19:59pm

OriginalGriff

Comments

Richard Deeming 13-Sep-19 12:33pm

F10 is also useful - when you're not debugging, it compiles, starts the application, and breaks on the first line of user code. :)

Richard MacCutchan · Answer 2 · 2019-09-11T21:44:00

Solution 2

See Overview of Visual Studio | Microsoft Docs[^].

Posted 11-Sep-19 21:44pm

Richard MacCutchan

phil.o · Answer 3 · 2019-09-11T22:37:00

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.

Posted 11-Sep-19 22:37pm

phil.o

Comments

[no name] 12-Sep-19 6:54am

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?