Bug 459 - Errors in "Application Output" are very hard to notice when running MT apps
Summary: Errors in "Application Output" are very hard to notice when running MT apps
Status: RESOLVED DUPLICATE of bug 460
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8 Alpha 2
Hardware: PC Mac OS
: --- major
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-08-25 19:17 UTC by Nat Friedman
Modified: 2011-08-29 18:15 UTC (History)
3 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 Nat Friedman 2011-08-25 19:17:56 UTC
Also the text in them is grey.


Comment 1 Mikayla Hutchinson [MSFT] 2011-08-25 20:56:53 UTC
It's in grey because the output (and the error) is from the mtouch tool that we use to run the app, not from the app itself. We can improve that by moving the code to run apps on the simulator into the MD addin itself, and report those kinds of errors in a dialog.

We could maybe mark the output pad's tab red for apps that end with a nonzero exit code?
Comment 2 Nat Friedman 2011-08-25 21:13:02 UTC
I think the text should be easier to read, and should be left on the screen if the app crashes.
Comment 3 Mikayla Hutchinson [MSFT] 2011-08-25 21:23:12 UTC
The text isn't an app crash.
Comment 4 Nat Friedman 2011-08-25 21:27:24 UTC
You're right but you're splitting hairs. If my app doesn't run at all, I need to know why. Right now MD leaves me alone in the cold.
Comment 5 Mikayla Hutchinson [MSFT] 2011-08-25 21:39:12 UTC
In general, it's important to have a way to distinguish the output of the app from the output of the tool that runs the app. That's why it's grey. Maybe we could make it some brighter colour, like blue. But the best solution in this case would be to allow MD to launch the app directly and report errors in an understandable way instead of making the user parse a tool crash.
Comment 6 Nat Friedman 2011-08-25 21:42:02 UTC
Let's use a brighter color. Even a brighter grey would be ok.

And let's make sure that the messages don't disappear when the app crashes. That is the larger issue.
Comment 7 Miguel de Icaza [MSFT] 2011-08-29 18:15:28 UTC
We will be checking the error at the MonoDevelop level, before we even ask mtouch to do anything.

And I want to do those checks for other bits there as well, so I am closing this bug (as it is a duplicate)

*** This bug has been marked as a duplicate of bug 460 ***