I think the way this was done is not good. Visual Studio does not
detect that NHibernate.ByteCode.Castle.dll is used so it doesn't put
it in the bin directory. So for every project I have to go add a
reference to this. That is a pain but I can deal with it, but the
bigger deal breaker is VSTS doesn't copy this DLL into the test
directory either and so far I haven't been able to get that to work.
>From a backwards compat point of view it would have been much nicer to
default the config option to Castle (since that is what it used
before) and to default the config option so it didn't have to be set.
I see zero downside to this so that people who cared about this could
use whatever they wanted but I suspect most people do not care at all
about switching out byte code providers and left to deal with this in
order to use the latest version - which is required for using LINQ for
NHibernate.


On Aug 2, 4:09 pm, mathmax <[email protected]> wrote:
> Fabio Maulo,
>
> My project was running with this config file and nh 2.0.1 like a
> charm. It works no more with nh 2.1.0.
>
> So, as far as I've understood, I need one of those new dll to make it
> work with nh 2.1.0:
> NHibernate.ByteCode.LinFu.dllNHibernate.ByteCode.Castle.dll
>
> Why do we need to use these two lines:
>       <property name="connection.isolation">ReadCommitted</property>
>       <property
> name="proxyfactory.factory_class">NHibernate.ByteCode.LinFu.ProxyFactoryFac­tory,
> NHibernate.ByteCode.LinFu</property>
>
> instead of this old code:
>       <property
> name="connection.provider">NHibernate.Connection.DriverConnectionProvider</
> property>
>       <property
> name="connection.driver_class">NHibernate.Driver.SqlClientDriver</
> property>
> ?
>
> I don't need lazy loading and NHibernate.ByteCode.LinFu.dll seems to
> be required only when using lazy loading, isn't it ?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to