21

Where can I find the latest version of NHibernate.ByteCode.LinFu.dll that is compiled against NHibernate 3.2?

sternr
  • 6,216
  • 9
  • 39
  • 63

2 Answers2

28

in NHibernate 3.2 you do not need NHibernate.ByteCode.LinFu.dll because NHibernate 3.2 implements the proxy by itself. so we need modify the config like as:

<property name=”proxyfactory.factory_class”>NHibernate.Bytecode.DefaultProxyFactoryFactory, NHibernate</property>
imzrh
  • 293
  • 3
  • 4
19

From 3.2, NHibernate ha its own embedded proxy generator: there are nо more need of NHibernate.ByteCode.LinFu.dll or NHibernate.ByteCode.Castle.dll and I don't think they are supported any more.

I think you have to download the last supported source of NHibernate.ByteCode.LinFu.dll source, and try to compile it against the 3.2.

Michele Lepri
  • 440
  • 3
  • 9
  • So when configuring the NHibernate Session factory, what type should I set as the ProxyFactory? – sternr Nov 28 '11 at 16:20
  • 1
    Are you using web/app.cofig or are you configuring NHibernate via c# code? In the first way you have to specify "codedom" (for CodeDOM based one), "lcg" (for Lightweight one) or a custom provider. Via c# code, you have to specify an istance of `NHibernate.Bytecode.CodeDom.BytecodeProviderImpl`, `NHibernate.Bytecode.Lightweight.BytecodeProviderImpl` or a custom one. – Michele Lepri Nov 28 '11 at 17:16
  • 3
    Ok, so This didn't work for me, what I had to do was use the following proxy factory: NHibernate.Bytecode.DefaultProxyFactoryFactory – sternr Dec 01 '11 at 11:19