ansaurus

Question

NHibernate and Windsor assembly conflicts

Answer 1

+2 A:

You could get the source for NHibernate.ByteCode.Castle and build a version that uses version 2.2.0.6628 of Castle.DynamicProxy2. The 2.1.x branch is here in svn.

It is also possible that an assembly binding redirect may work. This could fail due to API difference between 2.1 and 2.2 of Castle.DynamicProxy2.
You would also update the assembly references in your MVCApp project.

<configuration>
   <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
         <dependentAssembly>
            <assemblyIdentity name="Castle.DynamicProxy2" publicKeyToken="407dd0808d44fbdc"/>
            <bindingRedirect oldVersion="2.1.0.0" newVersion="2.2.0.6628"/>
         </dependentAssembly>
      </assemblyBinding>
   </runtime>
</configuration>

Lachlan Roche 2010-02-27 11:58:41

Hi Lachlan..thanks for the help...again. Will give it a try.

Matt 2010-02-27 13:13:50

Answer 2

+3 A:

From where did you get your NHibernate.ByteCode.Castle?

I believe that ActiveRecord 2.1 will have one built for the latest stable release of DynamicProxy2.

Otherwise, do what Lachlan Roche suggests.

jishi 2010-02-27 12:41:03

From the NHibernate-2.1.2.GA-bin sourceforge.net download.. thanks for the ActiveRecord option.

Matt 2010-02-27 13:17:31

Snapping NHibernate bytecode provider from AR is your best option for now, since NHibernate team does not provide updated download for DynamicProxy 2.2

Krzysztof Koźmic 2010-02-27 18:41:41

ansaurus

tags:

views:

answers:

NHibernate and Windsor assembly conflicts

related questions