When to update assemblies versions and when not

[John Simons]

There has been a few threads about people not being able to easily
(without having to recompile the whole thing) swap assemblies with the
latest ones.
http://groups.google.com/group/castle-project-devel/browse_thread/thread/9c4ecb75d81c1bf7/

Jono, proposed the following:
"So maybe the alternative is to not increment the assembly version but
the
file version for hotfix/patch releases (i.e. 2.0.1, 2.0.2). Which
means that
you could just drop in a patch release without worrying about updating
dependant libraries, this then ensures the user is using compatible
versions
and allows us to fix bugs that don't break public interfaces."

Which I think is a good idea. +1

What does everyone else think about this?

Cheers
John

[Krzysztof Koźmic]

+1

[SimoneB]

Is this how MS versions core assemblies like System.dll though .net fx
releases?

On Feb 13, 7:38 am, John Simons <johnsimons...@yahoo.com.au> wrote:
> There has been a few threads about people not being able to easily
> (without having to recompile the whole thing) swap assemblies with the

> latest ones.http://groups.google.com/group/castle-project-devel/browse_thread/thr...

[Markus Zywitza]

This results in the Apache Versioning Syndrom, having 2.2 deprecating
2.0 after a couple of years and some 70 patch releases that all some
new functionality...

However, it is practical, so +1 from me.

2010/2/13 John Simons <johnsi...@yahoo.com.au>:

> --
> You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
> To post to this group, send email to castle-pro...@googlegroups.com.
> To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
>
>

[Krzysztof Koźmic]

Valid point Markus,

I think we should only use that for point point releases and only for
fixes, not new functionality.

New functionality = new major and/or minor version

Krzysztof

[John Simons]

Sorry I didn't mention, yes this would only be used for point
releases.

Cheers
John

On Feb 13, 11:45 pm, Krzysztof Koźmic <krzysztof.koz...@gmail.com>
wrote:

> Valid point Markus,
>
> I think we should only use that for point point releases and only for
> fixes, not new functionality.
>
> New functionality = new major and/or minor version
>
> Krzysztof
>
> On 2010-02-13 13:41, Markus Zywitza wrote:
>
> > This results in the Apache Versioning Syndrom, having 2.2 deprecating
> > 2.0 after a couple of years and some 70 patch releases that all some
> > new functionality...
>
> > However, it is practical, so +1 from me.
>

> > 2010/2/13 John Simons<johnsimons...@yahoo.com.au>:

>
> >> There has been a few threads about people not being able to easily
> >> (without having to recompile the whole thing) swap assemblies with the
> >> latest ones.

> >>http://groups.google.com/group/castle-project-devel/browse_thread/thr...

[John Simons]

@Simone, Does it really matter what MS does?

[Jonathon Rossi]

It looks like Microsoft doesn't actually increment the assembly version at all for the .NET Fx. mscorlib in my GAC is 2.0.0.0, and System.Core is 3.5.0.0, so 3.5 or 3.5SP1 didn't change any versions even though they had red bits. If I had 1.0 or 1.1 of the Fx installed I would have those ones too.

--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.

--
Jono

[SimoneB]

I mentioned it just because since they invented it, then they might
have had some good ideas of how to employ it. In fact, although they
don't change assembly versions, they change file versions for core
assemblies with patches and SPs. For example, although System.dll has
assembly version 2.0.0.0, on my machine running Vista SP2 the file
version is 2.0.50727.4016, which is probably different on a different
OS: http://en.wikipedia.org/wiki/.NET_Framework_version_list

[Fabian Schmied]

+1

2010/2/13 Krzysztof Koźmic <krzyszto...@gmail.com>: