You could still use the old bytecode provider, but you have to compile it yourself.
Diego P.S.: you answered to me directly and not to the group, I've added it back. On Tue, Mar 12, 2013 at 8:19 AM, David Zwingelberg < [email protected]> wrote: > In my opinion it is a show stopper. If you are using lazy properties in > your environment you can not switch to a newer NHibernate version than 3.1. > Or is there any workaround I haven't considered? > > Am Montag, 11. März 2013 22:37:34 UTC+1 schrieb Diego Mijelshon: > >> Yeah, you are right. It's probably worth merging, but I don't know how >> big is the effort. >> >> >> On Mon, Mar 11, 2013 at 5:30 PM, Alexander I. Zaytsev >> <[email protected]>wrote: >> >>> Diego, it is fixed in master branch, which is going to be vNext not 3.3.3 >>> >>> >>> 2013/3/12 Diego Mijelshon <[email protected]> >>> >>>> It says in the last comment that it was fixed, but there hasn't been a >>>> new build out since then. >>>> >>>> >>>> On Mon, Mar 11, 2013 at 10:13 AM, David Zwingelberg < >>>> david.zw...@googlemail.**com> wrote: >>>> >>>>> Hi! >>>>> Are there any plans to support lazy properties in NHibernate 3 as it >>>>> documented in the issue NH-3058 (https://nhibernate.jira.com/** >>>>> browse/NH-3058 <https://nhibernate.jira.com/browse/NH-3058>)? >>>>> I am faced with the bug in the version 3.2.0 to 3.3.3. So I am still >>>>> using NHibernate in version 3.1.0 with the NHibernate.ByteCode.Castle. >>>>> **ProxyFactoryFactory which doesn't cause the problem. But I want to >>>>> profit from the linq features implemented in the next versions. >>>>> >>>>> Why is this problem not fixed in the NH3? Will the fix be merged in >>>>> 3.next? >>>>> >>>>> The attachement contains a solution which causes the problem as it is >>>>> used in my environment. >>>>> >>>>> -- >>>>> >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "nhibernate-development" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to nhibernate-development+**[email protected]. >>>>> For more options, visit >>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>>> . >>>>> >>>>> >>>>> >>>> >>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "nhibernate-development" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to nhibernate-development+**[email protected]. >>>> For more options, visit >>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>> . >>>> >>>> >>>> >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "nhibernate-development" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to nhibernate-development+**[email protected]. >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >>> >>> >> >> -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
