Start with debugging and Start without?
-
What is the difference? Either way the program runs. Only thing I noticed is when I use Start without debugging after I have viewed my output and hit a key then the "Press any key to continue..." pops up. Otherwise when I choose Start with debugging the program runs with no continue message. Isn't the debugger only used in the code editor window?
-
What is the difference? Either way the program runs. Only thing I noticed is when I use Start without debugging after I have viewed my output and hit a key then the "Press any key to continue..." pops up. Otherwise when I choose Start with debugging the program runs with no continue message. Isn't the debugger only used in the code editor window?
-
What is the difference? Either way the program runs. Only thing I noticed is when I use Start without debugging after I have viewed my output and hit a key then the "Press any key to continue..." pops up. Otherwise when I choose Start with debugging the program runs with no continue message. Isn't the debugger only used in the code editor window?
No, start with debugger means that your application will run in a virtualized environment where the signals, variables, and other stuff that program uses will be easily "seen". In the release mode, your program's code is compiled down to native code and you cannot debug it easily. In debug mode, your breakpoints can be set and you can stop the program (as Richard said in the post above), to check what is working and what is not. In release configuration, you get the best optimized native code to run on the machine; but you lose the debug stuff. In the code editor, that is IntelliSense, for auto correcting the code, or the background interpreter and compiler that keeps telling you where an error is occuring. That is not debugging, that is just making the syntax right. Of course the program starts, runs and executes. But there are various other issues, such as the errors are thrown and application breaks, you are not told anything about it. In such cases, logging is used.
Member 12974235 wrote:
Otherwise when I choose Start with debugging the program runs with no continue message.
We are sorry, since you have not shared any code sample with us we cannot understand why this happens. For more on this please read, What is the difference between Release and Debug modes in Visual Studio? - Stack Overflow[^]
The shit I complain about It's like there ain't a cloud in the sky and it's raining out - Eminem ~! Firewall !~
-
No, start with debugger means that your application will run in a virtualized environment where the signals, variables, and other stuff that program uses will be easily "seen". In the release mode, your program's code is compiled down to native code and you cannot debug it easily. In debug mode, your breakpoints can be set and you can stop the program (as Richard said in the post above), to check what is working and what is not. In release configuration, you get the best optimized native code to run on the machine; but you lose the debug stuff. In the code editor, that is IntelliSense, for auto correcting the code, or the background interpreter and compiler that keeps telling you where an error is occuring. That is not debugging, that is just making the syntax right. Of course the program starts, runs and executes. But there are various other issues, such as the errors are thrown and application breaks, you are not told anything about it. In such cases, logging is used.
Member 12974235 wrote:
Otherwise when I choose Start with debugging the program runs with no continue message.
We are sorry, since you have not shared any code sample with us we cannot understand why this happens. For more on this please read, What is the difference between Release and Debug modes in Visual Studio? - Stack Overflow[^]
The shit I complain about It's like there ain't a cloud in the sky and it's raining out - Eminem ~! Firewall !~