Bug 120 - Application output left open when custom run command fails
Summary: Application output left open when custom run command fails
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: Trunk
Hardware: PC Windows
: Low minor
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-07-30 20:11 UTC by Mikayla Hutchinson [MSFT]
Modified: 2016-10-24 11:37 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 Mikayla Hutchinson [MSFT] 2011-07-30 20:11:15 UTC
If a custom run command fails (for example, invalid working directory) then the application output pad is left open and active, and cannot be closed.
Comment 1 iain 2016-10-24 11:37:33 UTC
This seems fixed in 6.2 to me, but maybe I'm not testing it correctly.