Bug 723 - console can't close automatic when debug a console project
Summary: console can't close automatic when debug a console project
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: unspecified
Hardware: PC Windows
: Low normal
Target Milestone: ---
Assignee: Lluis Sanchez
Depends on:
Reported: 2011-09-10 12:57 UTC by minco
Modified: 2013-11-20 03:47 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description minco 2011-09-10 12:57:12 UTC
class MainClass
		public static void Main (string[] args)
			dynamic a = 1;
			a = 2;
Comment 1 Mike Krüger 2011-09-12 05:50:17 UTC
I'm not 100% sure what you mean with that bug report.

Do you mean that the output pad closes automatically when you select the editor ?
Comment 2 minco 2011-09-12 20:51:47 UTC
when I press F5 to run the application, it didn't auto close the cmd window
Comment 3 Mikayla Hutchinson [MSFT] 2011-11-16 15:46:06 UTC
Did you try unchecking "Pause console output" in project run settings?
Comment 4 PJ 2013-11-19 17:04:10 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 5 Lluis Sanchez 2013-11-20 03:47:54 UTC