Re: [Ikvm-developers] AssemblyVersion vs AssemblyFileVersion

[Bell, T. (E O C&S US) <tre...@si...>]

Jeroen, thanks and understood.

For patch releases though, since they are binary compatible, would it be
possible to leave the assembly version the same? 

It seems like this is one of the main reasons to have a separate
assembly version and an assembly file version.

In our shop it would allow us to deploy newer IKVM patches more
frequently, if we did not have to change anything in our projects
(app.config or assembly references). Unfortunately, there are a lot of
places where we have to coordinate these changes. If the assembly
version did not change, we only need to copy over the newer assemblies
and put them in the GAC.


-----Original Message-----
From: Jeroen Frijters [mailto:je...@su...] 
Sent: Thursday, September 01, 2011 9:12 AM
To: Bell, Trevor (E O C&S US); ikv...@li...
Subject: RE: AssemblyVersion vs AssemblyFileVersion

Bell, Trevor (E O C&S US) wrote:
> I realize that major changes to IKVM, such as new assemblies, and
public
> interface changes would mandate a change to the assembly version, but
I
> don't think this is happening on every release.

New releases usually really are binary incompatible, so this is very
much intentional.

For patch releases (e.g. 0.46.0.0 -> 0.46.0.1) there is binary
compatibility and it would be possible to generate a policy assembly to
automatically redirect (or you can use an app.config to "manually"
redirect).

Regards,
Jeroen