[MonoDevelop] constant minor, build version for monodevelop core libraries
Lluis Sanchez Gual
lluis at novell.com
Fri Nov 13 04:39:30 EST 2009
I'll see what can I do in Mono.Addins. In the meanwhile, addins using
compatVersion will have to keep their version numbers.
El dv 13 de 11 de 2009 a les 10:29 +0100, en/na Carlo Kok va escriure:
> On 11/12/2009 11:40 PM, Michael Hutchinson wrote:
> > On Thu, Nov 12, 2009 at 2:10 PM, Carlo Kok<ck at carlo-kok.com> wrote:
> >> Hi everyone,
> >> What about making the core dlls have only the major part of the assembly
> >> version set? So not every new minor build has to break all not included
> >> plugins (this could probably even help monotouch).
> >> The addin version with "compatVersion" settings mono.addins provides
> >> could define what range of versions it's really compatible with, but if
> >> the assembly version changes it doesn't even get to the point where it
> >> can decide if it can be loaded.
> > Maybe in cases where we're confident about the ABI compatibility and
> > are setting compatVersion we could also ship assembly publisher policy
> > files. Or perhaps this is something the the Mono.Addins assembly load
> > hook can handle automagically based on the compatVersion.
> If Mono.Addins could redirect the assembly references this would be
> ideal yeah (and of course the compatVersion would be set).
> > IMO either of these would be preferable to holding back the assembly versions.
More information about the Monodevelop-list