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.
When looking at the .app package produced by default MonoDevelop for a MonoMac application, the script responsible of launching the application do something rather weird as it first sets up an environment to use the latest Mono available on the platform (i.e. by pointing to /Library/Frameworks/Mono.framework/Versions/Current) but then end up using a bundled mono executable which version may not be existing in /Versions.
This make the application not start on user machines who don't have the bundled Mono version installed on their system (main reason being it can't load the right mscorlib.dll).
The fix would be to either exec the Mono executable found in /Versions/Current/bin instead of a bundled one or also bundle/link by default Mono inside the .app (as we do in case of AppStore submission).
So the change I made to make the package work with the system-available mono was simply to make the top-level mono binary a symlink to /Library/Framework/Mono.framework/Versions/Current/bin/mono
this is fixed in the monomac branch