The assembly version is the API version. The API has not changed, therefore the API i.e. assembly version hasn't changed. This is precisely to reduce the need for binding redirects and recompilation of dependent projects. This is also why the assembly version of e.g. the .Net framework itself never changes, despite a large number of service packs and other updates. (It will probably be less confusing in the future, my thinking is that the assembly version should be frozen at x.y.0.0 for all x.y.z releases.)
The real problem in my opinion is that MS introduced 4 version fields, but decided to arbitrarily only display one of them in Visual Studio, and to _not_ display this one in the regular File Properties. Hope this clarifies things. Like I said, the goal is to reduce the work required when upgrading to a new minor release within the same major series. Using a binding redirect to override 3.1 with 3.3 might be pushing it though. The new linq provider was introduced in 3.0. It has been greatly improved during subsequent 3.x releases, so it would be interesting to learn about anything that used to work but doesn't anymore. Either someone might be doing something inappropriate, or there might be a NH regression that we would like to fix. /Oskar 2013/10/11 Peter McEvoy <[email protected]> > I'm trying to upgrade to NH 3.3.3.4001, but need to use bindingRedirect > because a shared library that I have no control over is bound to 3.1 and is > unable to upgrade due to various NotSupportedExceptions that the 3.3.3 linq > driver now throws. > > However there are features in 3.3.3 that I would like to use in another > sln. After some struggling to get this to work, it appears that I am not > nuts, and that the NH nuget package 3.3.3.4001 contains a DLL whose > fileversion is 3.3.3.4001, but the assembly name is: "NHibernate, > Version=3.3.1.4000, Culture=neutral, PublicKeyToken=aa95f207798dfdb4" - > this means the bindingRedirect is not very intuitive. > > If this is intentional, can someone explain why? It's not very > intuitive.... > > Cheers > Pete > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/nhusers. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/groups/opt_out.
