Is there any real advantage in using and maintaining the Castle bytecode provider (over the new default one, that is)? If it's worth maintaining, it could be moved to NHibernate.Contrib or as a Castle contrib project.
-- Mauricio On Thu, May 26, 2011 at 1:06 PM, G. Richard Bellamy <[email protected]>wrote: > I’m curious what the status is of the NH bytecode provider from the Castle > perspective (if there is one). From what I’ve read, the NH team is no longer > supporting the various Bytecode providers, and is going with a default of > using LinFu for their ProxyFactoryFactory (I guess this really means they’re > no longer supporting the Spring and Castle bytecode providers). > > > > > http://groups.google.com/group/nhusers/browse_thread/thread/d22172aec62a2ddd/d6a8898a1204fc8f?lnk=gst&q=bytecode#d6a8898a1204fc8f > > > http://stackoverflow.com/questions/5728622/nhibernate-bytecode-providers-source > > > > -rb > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" 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/castle-project-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en.
