Bug 16761 - Sometimes the code editor always appears above other programs
Summary: Sometimes the code editor always appears above other programs
Status: RESOLVED DUPLICATE of bug 10644
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0.1
Hardware: PC Windows
: --- normal
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2013-12-12 17:46 UTC by Megan
Modified: 2013-12-12 18:10 UTC (History)
1 user (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 Megan 2013-12-12 17:46:10 UTC
I recently updated Unity to the latest version and it came with MonoDevelop 4.0.1. When working with MonoDevelop and Unity, sometimes the MonoDevelop editor gets to a point where it won't go behind any other programs, and even when bringing up the help menu or other modal windows within MonoDevelop, they show up behind it, forcing me to close the program and restart it.
Comment 1 Mikayla Hutchinson [MSFT] 2013-12-12 18:10:23 UTC
This was fixed long ago. Unfortunately Unity shipped a long out of date (8 months, 14 stable releases) version of MonoDevelop.

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