I hope that we will remove the "internal" DynamicProxy system... but when Microsoft will give us a good default DynamicProxy system (hopefully in .NET5 and overall outside EntityFramework). I think you can use the "internal" DynamicProxy in Envers for some years ;)
On Wed, Apr 11, 2012 at 5:47 PM, Roger Kratz <[email protected]>wrote: > Hi > > In Nhibernate Envers there are some hand written proxies. For different > reasons it would make my life easier to use some dynamic proxies instead. I > would prefer not having a dependency to some external proxy fw and > therefore started to look at using NH Core's proxy capabilities intead > (which envers already references). > > I first had an idea using NH Core's user's defined proxy fw > (Environment.ProxyFactoryFactoryClass) but the public API available was way > to NH Core specific to suit my needs. However - if using > NHibernate.Proxy.DynamicProxy.ProxyFactory directly (the "copy" from LinFu) > I can build the proxies the way I want to and everything is fine. The > things the bothers me a little bit is whether this is meant to be used from > a 3rd party lib (or an user)? Is there a high risk of removal/big changes? > > In short terms... If you in NH Core team would remove or change the > NHibernate.Proxy.DynamicProxy.ProxyFactory - would you see that as a > breaking change (=not that high risk that this internal proxy fw will be > removed/completly rewritten)? > > All the best > Roger > -- Fabio Maulo
