Missing "press any key to continue..." when lauching with CTRL+F5 - by vesterbaek

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 540969 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 3/10/2010 10:35:47 AM
Access Restriction Public


The following bug, closed as fixed in Visual Studio 2010 RC, is still there:

In my Makefile project, if I start the program without debugging (CTRL+F5), it always (per default) closed the opened console window. I compared my project file to a standard console application project file, and found the following:


Inserting this (using a text editor) under <Project> in my makefile project .vcxproj file solves the problem ... It would make sense that is the default behavior (as it is in my vs2005), or that this could be controlled from the standard project dialog.
Sign in to post a comment.
Posted by Micro Hard on 1/20/2011 at 8:52 PM
Linked to this from Google and I think I have the answer and an easier workaround.

This is not for the original poster, but for future Googlers like me. With the new visual studio 2010 you might see this behavior even when you use ctrl f5 aka "start without debugging". This is most likely because you created an "empty project" instead of a "Win32 console application". If you create the project as a "Win32 console application" you can disregard this as it does not apply.

In the older versions it would default to the console subsystem even if you selected "empty project", but not in 2010, so you have to set it manually. To do this select the project in the solution explorer on the right or left (probably is already selected so you don't have to worry about this). Then select "project" from the menu bar drop down menus, then select "*project_name* properties" > "configuration properties" > "linker" > "system" and set the first property, the drop down "subsystem" property to "console (/SUBSYSTEM:CONSOLE)". The console window should now stay open after execution as usual.
Posted by Microsoft on 7/12/2010 at 6:24 PM
Thank you for your feedback. Please note the workaround mentioned above. We will be unable to fix this issue in the next VS release given our other work items. However, if the status of this bug changes, I will update this bug to reflect the change in decision.
Posted by Microsoft on 7/9/2010 at 1:52 PM

This is a result of tags not correctly being added to the .vcxproj file. The workaround for this issue is to add a <SubSystem> tag to your project file in the <Link> section with the correct sub system. An example of this is:

We will be redirect this issue to the project system team to evaluate fixing this issue when the project file is created.

Best Regards,
Visual Studio Debugger
Posted by vesterbaek on 3/24/2010 at 9:35 AM
I'm using the RC. The about box says "Version 10.0.30128.1 RC1Rel"
Posted by vesterbaek on 3/24/2010 at 9:34 AM
I've attached a solution (console_1.zip) to this ticket.
What I did:
- Create console solution with win32 console application project
- Compile this project
- Add makefile project without specifying any make commands. Set debug path to $(SolutionDir)\Debug\console_1.exe
- Remove console project
- CTRL+F5 quickly opens window and closes it again ("press any key ...." is missing)
Posted by Microsoft on 3/23/2010 at 6:04 PM

We are unable to reproduce this with the RC. Is it possible the project you are using was created with Beta2 and so was missing the correct configuration information as you noted?

Best Regards,
Visual Studio Debugger
Posted by Microsoft on 3/10/2010 at 7:12 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you