Yes, you are right that the assembly version should change as the libraries
move on. The problem is that this is generally something that is done with
an official release, and not changing all the time on the trunk. I'm not
sure how this problem should be fixed while on the trunk without any
releases.
On Thu, Mar 5, 2009 at 7:44 AM, Henning <henning.ei...@googlemail.com>wrote:
>
> I understand the problem ... but on the other hand is RC3 build not
> compatible with a trunk build - at least not if you're using the
> NHFacility, because the NHFacility is strictly linked to a specific
> version of NH.
>
> So whenever such a strict linking is being changed, the
> AssemblyVersion should also change, because the Builds will not be
> compatible anymore. At least not, if you don't have the corresponding
> version of NH. (Leaving aside the fact, that method-signatures might
> also have changed and stuff).
>
> On 4 Mrz., 22:36, Jonathon Rossi <j...@jonorossi.com> wrote:
> > The reason is that if you change the assembly version in every build,
> > dependant libraries must also be rebuilt or configured with assembly
> > bindings to use the other version. This is the main reason a lot of
> > companies won't increment the assembly version for revisions or builds,
> only
> > major and minor versions. One example is the .NET FX, all the 2.0, 3.0
> and
> > 3.5 assemblies only contain the major.minor and exclude the rest.
> >
> >
> >
> > On Thu, Mar 5, 2009 at 7:07 AM, Victor Kornov <wee...@gmail.com> wrote:
> > > AFAIK, that is for a reason, some issue with versioning, but I don't
> > > remember why exactly.
> >
> > > On Thu, Mar 5, 2009 at 12:05 AM, Henning <henning.ei...@googlemail.com
> >wrote:
> >
> > >> That is actually not the problem, the AssemblyFileVersion is being set
> > >> alright.
> >
> > >> But look at the common-project.xml:
> >
> > >> --- cut --- cut --- cut ---
> > >> <property overwrite="false" name="assembly.version"
> > >> value="$
> > >> {project.major}.${project.minor}.${project.build}.0" />
> > >> <property overwrite="false"
> > >> name="assembly.version.informational"
> > >> value="${assembly.major}.${assembly.minor}.${assembly.build}.$
> > >> {svn.revision}" />
> > >> --- cut --- cut --- cut ---
> >
> > >> You will notice, that the assembly-version is ignoring the subversion
> > >> revision, and thus is going to interfere with my existing RC3 in the
> > >> GAC.
> >
> > --
> > Jono
> >
>
--
Jono
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Castle Project Users" group.
To post to this group, send email to castle-project-users@googlegroups.com
To unsubscribe from this group, send email to
castle-project-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/castle-project-users?hl=en
-~----------~----~----~----~------~----~------~--~---
