2008/10/7 MAMMON <[EMAIL PROTECTED]> > but it DOES: > + Force me to make all of my methods and properties virtual, for the > use of proxies
It is not NH. It is a requirement of Castle.DynamicProxy and in general a requirement of any kind of DynProxy. Unluckily .NET don't give us a buildin system but, perhaps, we can do something using post#. > + Force me to override Equals() and GetHashCode(), because of proxies Not for sure. That is a best-practices if you are going to use ISet or if you are using composite-ID embedded in the class instead have a separate class for it. > + Prevent me from putting logic in public property getters/setters, > because the proxies, upon hydrating objects, would incorrectly execute > that logic. Not that is only your way to work. Who are using access trough fields don't have that problem (and NH have a lot of access strategy). > > + Create the "polymorphic databinding" problem with lists and > collections of objects, because of proxies. No. NH give you the ability to write your own IUserCollectionType... the "problem" here is that nobody have time to write something to share with the community or nobody are really interested to have that feature. -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
