Bug 39823 - "Run on external console" doesn't
Summary: "Run on external console" doesn't
Status: RESOLVED ANSWERED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 6.0.0 (C7)
Hardware: PC Mac OS
: --- normal
Target Milestone: master
Assignee: David Karlaš
URL:
Depends on:
Blocks:
 
Reported: 2016-03-21 22:35 UTC by Michael Teper
Modified: 2016-03-23 07:41 UTC (History)
2 users (show)

Tags:
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:
Status:
RESOLVED ANSWERED

Description Michael Teper 2016-03-21 22:35:51 UTC
I have a console app that expects user input via Console.ReadLine. In VS, a new command prompt is launched on debug and everything works as expected. In Xamarin Studio (OS X), no Teminal window opens and instead the Application Output pad auto-feeds newlines into my app. Checking the "Run on external console" option in Options makes no difference.

=== Xamarin Studio ===

Version 6.0 (build 4801)
Installation UUID: c939eca6-4745-4582-8b8e-c0d32beec616
Runtime:
	Mono 4.4.0 (mono-4.4.0-branch/f8474c4) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 404000040

=== Xamarin.Profiler ===

Not Installed

=== Xamarin.Android ===

Not Installed

=== Xamarin Android Player ===

Not Installed

=== Apple Developer Tools ===

Xcode 7.3 (10183.3)
Build 7D175

=== Xamarin.iOS ===

Not Installed

=== Xamarin.Mac ===

Version: 2.8.0.58 (Business Edition)

=== Build Information ===

Release ID: 600004801
Git revision: f73f730c738baf8701a5892b7af64fd468d1dc0c
Build date: 2016-03-14 14:28:06-04
Xamarin addins: 3af7be6c701eb0137645a03e38b82f23b65738c3
Build lane: monodevelop-lion-cycle7

=== Operating System ===

Mac OS X 10.11.4
Darwin Michaels-MBP 15.4.0 Darwin Kernel Version 15.4.0
    Fri Feb 26 22:08:05 PST 2016
    root:xnu-3248.40.184~3/RELEASE_X86_64 x86_64
Comment 1 David Karlaš 2016-03-22 13:28:46 UTC
I can't reproduce this...
1) Is there something special about your project?
2) Can you try creating new console project and try to reproduce it?(I'm wondering if it's environment or project specific)
3) Do you use some customizations of Terminal?
4) If you enable "Run on external console" is text still printed into "Application Output" pad?
Comment 2 Michael Teper 2016-03-22 18:13:29 UTC
1. Nothing special, a C# console app created with VS 2015.
2. Will try, will let you know results.
3. None.
4. Yes.
Comment 3 Michael Teper 2016-03-22 22:11:31 UTC
I think I've figured it out. XS is inconsistent about how it displays platform targets (x86 vs. Any CPU) where one shows up as "Debug|x86" and the other just "Debug". I was setting the checkbox on the wrong target. Once I realized my mistake and set the right checkbox, XS does the right thing.

This bug report can be re-targeted (forgive the pun) to make target display in dropdown lists consistent.
Comment 4 David Karlaš 2016-03-23 07:41:36 UTC
If you think configurations settings/current configuration selection is not clear enough, please open new bug report. Preferably with screenshots explaining what you would like to be changed.

Thank you,
David