David, That's interesting - I'm working on a fairly large in production app using EF at the moment. We're not using POCO and currently have 259 tables in the EDMX.
What's the magic number that you ran into? I also must admit that I agree with a lot of the things that Scott and some of the other posters have said. While EF does generate some quite interesting SQL under the covers the majority of the time it has been reasonable enough for our purposes. For the times that it hasn't we have custom rolled a few stored procs to cover the issues. Neil. On 13 April 2012 18:53, <djones...@gmail.com> wrote: > There are limitations to EF. A project here was started with ef but soon ran > into obstacles when the number of tables mapped was greater than the number > possible in ef. It's now using hand written dal that is a damn sight faster > as well. > > EF / NHibernate are tools, use the right tool for the right job. > > Davy > Hexed into a portable ouija board. > ________________________________ > From: Arjang Assadi <arjang.ass...@gmail.com> > Sender: ozdotnet-boun...@ozdotnet.com > Date: Fri, 13 Apr 2012 11:05:45 +1000 > To: ozDotNet<ozdotnet@ozdotnet.com> > ReplyTo: ozDotNet <ozdotnet@ozdotnet.com> > Subject: Re: Dump EntityFramework for LLBLGen > > One Word: EF Code First! and I haven't looked back ever since. > DAL is dead, Long live Entities > > Regards > > Arjang > On 13 April 2012 10:59, <ifum...@gmail.com> wrote: >> >> Been using llbLgen for years but finding that EF would do what i need. >> >> >> >> Would save me a step(time) using EF in vs 2010 instead of generate DAL >> using LLblgen >> >> >> >> Anyone have an opinion on this? >> >> >> >> >> >> Anthony > >
