Bug 4844 - Execution errors are hidden and not logged
Summary: Execution errors are hidden and not logged
Status: NEW
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Management ()
Version: Trunk
Hardware: PC Mac OS
: Normal enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-05-02 18:21 UTC by Mikayla Hutchinson [MSFT]
Modified: 2016-10-28 16:34 UTC (History)
3 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 for Bug 4844 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description Mikayla Hutchinson [MSFT] 2012-05-02 18:21:03 UTC
Execution errors - when an execution handler fails - are hidden because MD focuses the output pad, which causes the text editor to lose focus, and the text editor's search view clears the status bar when it loses focus.

The text editor should probably use a statusbar context, and just remove that, instead of potentially clearing other messages. Or, we could just wait until we have a notification system, which will fix it too.

The errors are also not logged, so there's no way to get the details of the exceptions. This makes it very hard to diagnose errors in execution handlers.
Comment 1 PJ 2013-11-19 16:32:20 UTC
This bug was targeted for a past milestone, moving to the next active milestone.