Fabio, that's a great idea! Thanks for your work on that.
Thanks also to Phillip for the code!
I'll have to try porting my extension to the castle bytecode provider
over to the NHibernate one. :)
BTW, are there any NHibernate features that the proxy does not support
at this point? Or have all the appropriate adjustments been made?
Patrick Earl
On Sun, Mar 20, 2011 at 3:28 PM, Fabio Maulo <[email protected]> wrote:
> Work done!!!
>
> On Sat, Mar 19, 2011 at 1:50 PM, Stephen Bohlen <[email protected]> wrote:
>>
>> This is great news for the improved ease-of-adoption (and packaging too,
>> of course) story for NH. Excellent to hear--!
>>
>> Steve Bohlen
>> [email protected]
>> http://blog.unhandled-exceptions.com
>> http://twitter.com/sbohlen
>>
>>
>> On Sat, Mar 19, 2011 at 12:43 PM, Fabio Maulo <[email protected]>
>> wrote:
>>>
>>> Hi all (team and users).
>>> I'm happy to announce that, at the end of this month, we have to release
>>> NHibernate3.2.0Alpha1.
>>> For real we can release 3.2.0 as GA but I would take some caution.
>>> With the release of NHibernate3.2.0Alpha1 we will remove all Bytecode
>>> providers because we will have our default.
>>> Each framework, as Castle, LinFu and Spring.NET, can deploy his own
>>> bytecode provider for NHibernate directly with their packages.
>>> Have a nice time.
>>> --
>>> Fabio Maulo
>>
>
>
>
> --
> Fabio Maulo
>
>
