Bad Assembly binding version in web.config for NH ?


I don't understand the NH version in lib, is it or ???

It has been upgraded and patch to,


this is the fileversion appearing in windows properties,

but vs2012 sees it as a ???
Should we upgrade assembly binding, is there some pb in assembly version number ?
Closed Dec 3, 2013 at 7:39 PM by sebastienros


sebastienros wrote Jul 23, 2013 at 2:21 PM

NH doesn't always update the assembly version even if the file version has changed. I will check.

CSADNT wrote Jul 23, 2013 at 3:18 PM

In the actual state the version is the same, and changing assembly binding is NOK.
But code has chnage and assembly version not ? This could lead to problems from the old dllhell times ?

Jetski5822 wrote Jul 24, 2013 at 8:57 AM

In this instance there shouldn't be any issues from the old dll. They are binary compatible if you are thinking that might be an issue.

CSADNT wrote Jul 24, 2013 at 12:28 PM

Ok, thanks for follow up, but I am still puzzled by the fact that NH generates assemblies with different internal code and same version, even if file version is different.
That's not the proof of a great quality.

BertrandLeRoy wrote Jul 25, 2013 at 7:39 PM

You may want to file a bug against them, then. We're not going to comment on the quality of their code, but you are free to do so...

CSADNT wrote Jul 25, 2013 at 8:26 PM

That's not m'y question, I simply raise a warning when I see a configuration which is well known to have been at the origin of many problems...
you don't fond This strange ? Different code, same version ?

BertrandLeRoy wrote Jul 25, 2013 at 10:59 PM

Not sure what your question is. I do think a different version should have a different version number, but we are in no position to impose that on them. They are a separate project. I don't see any problem with it however if it's not in the GAC.