Bug 1590 - Assembly versions should match addin versions
Summary: Assembly versions should match addin versions
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: Trunk
Hardware: PC Mac OS
: Lowest normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-10-19 19:13 UTC by Mikayla Hutchinson [MSFT]
Modified: 2015-07-31 09:52 UTC (History)
4 users (show)

Tags:
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:
Status:
RESOLVED NOT_ON_ROADMAP

Description Mikayla Hutchinson [MSFT] 2011-10-19 19:13:00 UTC
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.
Comment 1 Lluis Sanchez 2011-10-21 06:34:19 UTC
This used to be a problem in the past. Add-ins built against the assembly MonoDevelop.Core 2.8.0.0 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.
Comment 2 Mikayla Hutchinson [MSFT] 2011-10-21 07:36:57 UTC
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?
Comment 3 Alan McGovern 2011-11-15 15:07:11 UTC
Is this a problem then or can this just be closed?
Comment 4 Marius Ungureanu 2013-08-12 07:54:29 UTC
I think Lluis fixed this.
Comment 5 Lluis Sanchez 2015-07-31 09:52:26 UTC
We are not changing the version numbers due to the problem described above.