[MonoDevelop] Running two instances of MonoDevelop

[Todd Berman]

yes and no.

The one instance only was put into place to allow double clicking from 
nautilus and other operations to work as expected.

The 'easy' way to fix this, would be add a new commandline argument 
--new-process or something, that would avoid checking for the socket or 
starting a new one, and just startup normally. The issue with this will 
be that if you close the first one, and double click in nautilus, you 
will get another 'first' copy of MonoDevelop, as the second one, 
launched with --new-process isn't listening on the socket.

Eventually, using something like DBus could make this problem a lot 
easier to solve, however right now, its not a common enough component on 
most people's systems to make it a usable dep (imo).

--Todd

Phil Crosby wrote:
> Right now this appears to be impossible; running a second instance of
> monodevelop brings the first forward.
> 
> It would be nice to be able to run two instances so that browsing two
> solutions or working on them independently but at the same time could be
> easier. What are the technical barriers for this in the current version?
> 
> -Phil Crosby
> 
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-list
>