Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Today, with MonoDevelop master, if you try to open a DLL file, it will create an empty solution file and open it, instead of opening the assembly browser.
(This may be a duplicate of bug 1764, but having a regression in such a feature would be weird. Plus, that bug is on Mac, maybe the bug was not fixed in Linux?)
You need to select the assembly browser to do it - it's possible in the open dialog.
The default is to open the .dll as solution (I don't know the use case for that - but it's a feature).
Mike, did you read the linked bug? This is a regression.
@lluis: Do you know why we're using the solution workbench for that ?
I've no idea why we do it - that's why I don't sort the display bindings. I think too it's the assembly browser job to do it. But I thought that there is a secret master plan behind the solution workbench decision.
The reason is explained here:
Opening the assembly browser by default probably makes more sense.
Fixed by https://github.com/mono/monodevelop/pull/282