As has been pointed out elsewhere, ActiveRecord RC3 was compiled against NHibernate 1.2.
I can confirm from personal experience that it isn’t a great idea to try and swap in NHibernate 1.2.1 and assume everything will continue to function.
While it is true that you can using binding redirects to get most of the way there, dont’ forget that some tools like FxCop don’t respect these.
<runtime\> <assemblyBinding xmlns\="urn:schemas-microsoft-com:asm.v1"\> <dependentAssembly\> <assemblyIdentity name\="NHibernate" publicKeyToken\="aa95f207798dfdb4" culture\="neutral" /> <bindingRedirect oldVersion\="126.96.36.19900" newVersion\="188.8.131.5200" /> </dependentAssembly\> </assemblyBinding\> </runtime\>
I’m listening and watching the apology to the Stolen Generations from Australia’s Prime Minister Kevin Rudd on behalf of the Australian Parliament.
I teach my children that when they’ve done the wrong thing, when they’ve hurt someone, that they should say sorry.
I think it is right and proper that this standard should also apply at the highest levels.
This is an incredibly significant day. I hope it goes some way to helping those affected directly and indirectly.
If you ever get this error from TFS, then double-check that the item you’re requesting does actually exist in the repository. I was having this problem with one of our projects, where I was asking TFS for the latest version of this item:
$/Online Services Solution Template/Main/Source
But after much investigation (including querying the TFS SQL database directly) I discovered that the correct item name was in fact:
$/Online Services Solution Templates/Main/Source
So another way to read that error message would be as “I can’t find an item with that name, are you sure you typed it correctly?”