Find the project in Solution Explorer, right-click on the project –>; Property – & gt; Configure properties –> L Linker –> System – & gt; Subsystem (on the right side of window) –>; SUBSYSTEM:CONSOLE) SUBSYSTEM drop down box select CONSOLE (/SUBSYSTEM:CONSOLE).
Author Archives: Robins
Flash back record of vs2017 installation process
Of stroke vs_Enterprise. The exe running to flash back, as shown can’t install might have been caused by the following problems:
1, original vs installer damaged; C:\Program Files (x86)\Microsoft Visual Studio Installer;
2, not compatible with the existing system;
: change the vs_enterpree. exe property for compatibility (compatible with your system and open with the administrator);
Three solutions to flash back of program running result box under vs
When writing C/C ++ programs in VS, the result box will always flash away, and you can’t see the results of the program. This is really annoying, so here are three ways to solve it
Method one:
In the return 0; Before the statement, add a getchar(); In this case, getchar will wait for input, and the result box will display the result of the program.
As shown in the figure below:
Method 2:
Add the statement system(“pause”) at the end of the program; , plus the header file #include< stdlib.h> “, which will display the results after running them and prompt you to press any key to continue.
As shown in the figure below
Method 3:
To modify the project configuration, right-click on the project, select Properties from the right-click menu, and then select “Configuration Properties –>” from the list to the left of the pop-up dialog. The linker – & gt; System “, and then in the list on the right, in the first “subsystem” value, select “Console (/SUBSUSTEM:CONSOLE)”
As shown in the figure below:
From:
https://blog.csdn.net/rannianzhixia/article/details/66968219?locationNum=6& fps=1
Method one:
In the return 0; Before the statement, add a getchar(); In this case, getchar will wait for input, and the result box will display the result of the program.
As shown in the figure below:
Method 2:
Add the statement system(“pause”) at the end of the program; , plus the header file #include< stdlib.h> “, which will display the results after running them and prompt you to press any key to continue.
As shown in the figure below
Method 3:
To modify the project configuration, right-click on the project, select Properties from the right-click menu, and then select “Configuration Properties –>” from the list to the left of the pop-up dialog. The linker – & gt; System “, and then in the list on the right, in the first “subsystem” value, select “Console (/SUBSUSTEM:CONSOLE)”
As shown in the figure below:
From:
https://blog.csdn.net/rannianzhixia/article/details/66968219?locationNum=6& fps=1
2、 Solutions to the problem of flash back in vs2017
1,
“Project1.exe” (Win32): “C:\Users\Administrator\Documents\Visual Studio 2017\Projects\Project1\Debug\Project1.exe” has been loaded. Loaded symbol.
“project1.exe” (Win32): “C:\Windows\SysWOW64\ntdll.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\kernel32.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\ kernelbase.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\msvcp140d.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\ Syswow64 \ VCruntime140d.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\ ucrtbase.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\api-ms-win-core-timezone-l1-1-0.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\api-ms-win-core-file-l2-1-0.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\api-ms-win-core-localization-l1-2-0.dll” has been loaded.
“project1.exe” (Win32): “C:\Windows\SysWOW64\api-ms-win-core-localization-l1-2-0.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\api-ms-win-core-synch-l1-2-0.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\ api-ms-win-core-processThreads-l1-1-1.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\api-ms-win-core-file-l1-2-0.dll” has been loaded. The PDB file could not be found or opened.
program “[1176] project1.exe” has exited with a return value of 0 (0x0).
Solutions:
Step 1. Tick
tool ->; Options – & gt; Debugging – & gt; Conventional – & gt; Start source server support;
Start the source server to support the following three columns without checking;
>
>
>
>
Step 2. Tick
tool ->; Options – & gt; Debugging – & gt; Symbols – & gt; Microsoft Symbol Server;
Make sure
is selected in the pop-up dialog box;
Second problem: Flash back problem
Add system(“pause”) to the last line of code; Can be
“Project1.exe” (Win32): “C:\Users\Administrator\Documents\Visual Studio 2017\Projects\Project1\Debug\Project1.exe” has been loaded. Loaded symbol.
“project1.exe” (Win32): “C:\Windows\SysWOW64\ntdll.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\kernel32.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\ kernelbase.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\msvcp140d.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\ Syswow64 \ VCruntime140d.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\ ucrtbase.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\api-ms-win-core-timezone-l1-1-0.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\api-ms-win-core-file-l2-1-0.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\api-ms-win-core-localization-l1-2-0.dll” has been loaded.
“project1.exe” (Win32): “C:\Windows\SysWOW64\api-ms-win-core-localization-l1-2-0.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\api-ms-win-core-synch-l1-2-0.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\ api-ms-win-core-processThreads-l1-1-1.dll” has been loaded. The PDB file could not be found or opened.
“project1.exe” (Win32): “C:\Windows\SysWOW64\api-ms-win-core-file-l1-2-0.dll” has been loaded. The PDB file could not be found or opened.
program “[1176] project1.exe” has exited with a return value of 0 (0x0).
Solutions:
Step 1. Tick
tool ->; Options – & gt; Debugging – & gt; Conventional – & gt; Start source server support;
Start the source server to support the following three columns without checking;
>
>
>
>
Step 2. Tick
tool ->; Options – & gt; Debugging – & gt; Symbols – & gt; Microsoft Symbol Server;
Make sure
is selected in the pop-up dialog box;
Second problem: Flash back problem
Add system(“pause”) to the last line of code; Can be
Visual studio console program output window flashed by
Write at the front:
This blog post introduces a little annoying problem solving that isn’t a bug. Programming with Visual Studio often uses the console output window, but there is always a situation where the window flashes past and it is difficult to see the output of the program. Here, I write a blog post to record it, so as not to forget or make similar mistakes in the same type of problem.
Solution:
1. In the last line of the program, return 0, add system(” pause “) or getchar(); It solves some problems, which I often do when I do some OJ tests in order to test in my IDE;
2. Don’t Press F5 to run the program, Ctrl + F5 instead, a window will be displayed like this: “Press any key tocontinue…” The words. The reason is that F5 is in Debugging mode, while CTRL +F5 is in Start Without Debugging mode. I found this on the Internet. Can really solve the problem, but their lack of practical theoretical knowledge to support, so in the future to read a lot of attention to the process.
The problem of black box flash away in vs2019 debugging
VS2019 debugging when the black box flash away
Solution: Tools –> Options – & gt; Debugging
icon:
Solution for flash back of vs2015 running interface
Plan a
The return 0 statement is preceded by getchar ().
Scheme 2
Before the statement return 0, add a system(“pause”).
Plan 3
The return 0 statement is preceded by getchar ().
Scheme 2
Before the statement return 0, add a system(“pause”).
Plan 3
- Open View — Other Window — Property Manager Linker –>; System – & gt; SUBSYSTEM click the down arrow on the right side of the SUBSYSTEM, select the ‘/ CONSOLE’ link option, apply and confirm.
Solution to the problem of console output window’s CMD flashing back when vs2015 writes C + + program
1. Open project properties
2. Locate the linker and select System.
3. Select “/ CONSOLE” in the SUBSYSTEM
4. Execute (Ctrl + F5) at this point and the window will not flash back. Note that if you are debugging (F5), it will still flash back.
Flashback problem of output window of visual studio 2017 console program
When you first come into contact with Visual Studio, most people will write a Hello World program to try. Some people will find that the output window will flash past after execution, and there is no “Press any key to continue”. This has happened in Visual Studio 2008, 2010, 2012, 2015, and now 2017, and some people might do it one of two ways:
Add system(“pause”) or getchar() at the end of the program code. In fact, this is a command under DOS.
Example:
Add system(“pause”) or getchar() at the end of the program code. In fact, this is a command under DOS.
Example:
#include "stdio.h"
int main()
{
printf("hello world\n");
system("pause");
}The problem is that when you Press F5, the correct one should be Ctrl+F5, and the window will display Press any key to continue… That’s it. You can also see the results of the program run.
This is because F5 is in Debugging mode, where the window does not remain open once the application finishes running. If CTRL +F5 is in Start Without Debugging mode, you’ll be able to see the results.
If you press Ctrl+F5 and it still flashes, then use the following Settings:
In the top navigation bar, click “Project” –>; “Properties” – & gt;” Configure property “–>” The linker – & gt; “” System – & gt; “” Subsystems (there is a drop-down icon to the right of the window) “–>; SUBSYSTEM:CONSOLE The drop down box selects’ /SUBSYSTEM:CONSOLE ‘– gt; Finally “confirm” –>; Click on the top right corner “file “–>; “Save it all.”
// Finally, press Ctrl + F5 to avoid the flashback problem.
The problem of running result window flash of vs2015
Most novices writing console programs in VS for the first time will have a problem with a flash window of results. Most of the time this is not caused by a programming error, but by a detail we have overlooked.
The quick and easy solution is as follows:
1. Open the configuration window in the following order: Project ->; Property – & gt; Configure properties ->; The linker – & gt; System – & gt; The subsystem
2. Click the down arrow on the right side of the SUBSYSTEM, select the link option “/ CONSOLE”, apply and confirm it.
The reasons and common solutions of vs flash back on the road of C + + Learning (with reasons attached)
First of all, it’s normal to flash and go away.
Because the program statement is executed sentence by sentence, nothing makes it pause, at the speed of computer execution, of course, flash by.
What we need to do is make the system wait and pause so that it doesn’t flash back (some compilers automatically add this feature at the end of the code to prevent novice users from seeing the output).
Because the program statement is executed sentence by sentence, nothing makes it pause, at the speed of computer execution, of course, flash by.
What we need to do is make the system wait and pause so that it doesn’t flash back (some compilers automatically add this feature at the end of the code to prevent novice users from seeing the output).
1) add system(“pause”) before return;
Note: system() is the call to the system command; Pause command; “Press any key to continue..”
;
;
;
Note: getchar reads the next character, so it “pauses” while waiting for us to type.
It’s worth noting that sometimes you might need to add two getchar(), because the first getchar() might eat the carriage return or something like that.
3) Press Ctrl +F5 to run
Note: Ctrl +F5 is a program that debugs without debugging. It automatically “pauses” at the end of the program, so the DOS command prompt “Press any key to continue….” is added.
The little triangle we clicked on, which starts debugging (F5), does not automatically add “pause”, so it will flash past.
The above is only the idea after I consult the data to think, welcome everyone fellow middlemen to give correct, next will be very grateful!
Solution to the flash of visual studio console program output window
When you first come into contact with Visual Studio, most people will write a Hello World program to try. Some people will find that the output window will flash past after execution, and there is no “Press any key to continue”. This happens in both Visual Studio 2008, 2010, and 2012, and some people might do it one of two ways:
Add system(“pause”) or getchar() at the end of the program code. In fact, this is a command under DOS.
The problem is that when you Press F5, the correct one should be Ctrl+F5, and the window will display Press any key to continue… That’s it. You can also see the results of the program run.
This is because F5 is in Debugging mode, where the window does not remain open once the application finishes running. If CTRL +F5 is in Start Without Debugging mode, you’ll be able to see the results.
If you press Ctrl+F5 and it still flashes, then use the following Settings:
Right-click on Project –>; Property – & gt; Configure properties –> Connector – & gt; System – & gt; Subsystem (on the right side of window) –>; SUBSYSTEM:CONSOLE Drop down SUBSYSTEM selection CONSOLE