Really depends on the application.. if you are going for DDD then you can use both EF and CSLA. See here for Rocky's take on it
www.lhotka.net/weblog/ADONETEntityFrameworkLINQAndCSLANET.aspx On Thu, Jun 2, 2011 at 2:57 PM, Kirsten Greed <[email protected]> wrote: > Hi All > > Is anyone using http://www.lhotka.net/cslanet/ > > I am thinking EF4 may be good for reading and writing data from tables – but > not for implementing domain logic. > > Kirsten > > > > ________________________________ > > From: [email protected] [mailto:[email protected]] > On Behalf Of Greg Keogh > Sent: Thursday, 2 June 2011 12:14 PM > To: 'ozDotNet' > Subject: RE: building the domain model - what tools to use? > > > > Folks, I’ve also been trying to do exactly the same thing as Kirsten in the > EF4 model designer. > > > > I want to make an Entity which is a “view” of a few joined tables. You can > easily make the entity and add scalar properties to it, but my attempts to > map the properties to the underlying table columns doesn’t work via any > tricks I can find. Part of the problem is the understanding the cluttered > mapping control, and part is the incomprehensible slew of compile errors > that are generated. > > > > After all, I’m asking to do what ORM is designed to do, but I’m flummoxed as > well. I’ll try and find the relevant parts of Julia Lerman’s book and read > them again, and again. She must do this somewhere in the book. > > > > Greg > > __________ Information from ESET NOD32 Antivirus, version of virus signature > database 6172 (20110601) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com
