To be clear...CSLA should be base on Interfaces instead concrete class implementation.
2009/4/25 Fabio Maulo <[email protected]> > Make BusinessBase/BusinessList and so on, less closed to be used with > others frameworks and less oriented to pure ADO.NET > P.S. > I don't want remember how many problems I had in my first commercial > application using NH and CSLA. > > 2009/4/25 sturdytree <[email protected]> > > >> With CSLA.net, all domain classes need to inherit from Businessbase, >> which contains non-virtual properties. >> >> When using NHibernate, we need to implement virtual properties for >> lazy loading. >> >> Some options to use CSLA/NHibernate together seem to be: >> >> - switch lazy loading off in NHibernate and implement lazy loading >> code in the domain classes (although this seems less flexible) >> - leave lazy loading on in NHibernate but use a DTO class to map to >> the database and then transfer the data to the CSLA domain >> classes >> >> What other options might there be? Any pointers in the right direction >> will be much appreciated. >> >> I suppose the above question is really applicable to using NHiberntate >> with any framework. >> >> >> >> >> > > > -- > Fabio Maulo > -- 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 -~----------~----~----~----~------~----~------~--~---
