Why has NHibernate 3.3.3.4001 assembly version 3.3.1?

3
votes

I'm trying to resolve some assembly binding redirects for NHibernate 3.1 to 3.3.3.4001. I've not been having much luck with the following:

        <dependentAssembly>
            <assemblyIdentity name="NHibernate"
                              publicKeyToken="aa95f207798dfdb4"
                              culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-3.3.3.4001"
                             newVersion="3.3.3.40001" />
        </dependentAssembly>

The DLL properties indicate the file version is 3.3.3.4001, however DotPeek says that the FQ AssemblyName is "NHibernate, Version=3.3.1.4000, Culture=neutral, PublicKeyToken=aa95f207798dfdb4".

What's going on here?

1
nhibernate
possible duplicate of dll versions displayed in visual studio .Net not reflecting the referenced dll file/product versions – cremor

1 Answers

2
votes

See this NHibernate-Development group post.

NHibernate 3.3.3.SP1 keeps the previous assembly version so it's a drop in replacement for 3.3.1 - 3.3.3.

I am not sure why this is the case, maybe something todo with NuGet etc, Did you try using newVersion="3.3.1.4000"