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.
Assembly versions should match addin versions. The mismatch is a common source of confusion when users see addin engine errors and look at the list of loaded assemblies in the about box.
This used to be a problem in the past. Add-ins built against the assembly MonoDevelop.Core 220.127.116.11 would not load on an MD with a MonoDevelop.Core with a different version. That's why I keep assembly versions numbers when MD releases are backwards compatible.
Well, that's unfortunate, because it does confuse people that the assembly versions are for some slightly older version of MD. We'd almost be better off without assembly versions at all. Maybe we could fix this with bindingRedirects?
Is this a problem then or can this just be closed?
I think Lluis fixed this.
We are not changing the version numbers due to the problem described above.