Bug 3612 - Another instance of MonoDevelop is opened when opening a .CS file in Window Explorer
Summary: Another instance of MonoDevelop is opened when opening a .CS file in Window E...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8.6
Hardware: PC Windows
: Low normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-02-23 11:55 UTC by Eric Beisecker
Modified: 2015-08-20 13:28 UTC (History)
5 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 Eric Beisecker 2012-02-23 11:55:59 UTC
Current Behavior: With MonoDevelop opened, when a User double clicks on a .CS file in Windows explorer that is associated with MonoDevelop a NEW instance of MonoDevelop is opened.

Expected Behavior: The File should be opened in the already open Instance of MonoDevelop. 


MonoDevelop: RC2
.Net 4.0 Framework
Comment 1 Daniele 2012-04-11 16:55:10 UTC
I confirm this also on MD (on Windows 7).
Comment 2 Eklavya Mirani 2014-03-02 08:06:56 UTC
This has been solved, right?

I can't reproduce this anymore. (old bug, but status isnt resolved yet)
Comment 3 Lluis Sanchez 2015-08-20 13:28:23 UTC
It seems to be fixed.