[dba-VB] ADO.NET Entity Framework - to use or not?

I have used both nettiers and Entity Framework.

There are 3 of us that are creating commercial apps right now.
One app is done in nettiers. The others are being built using
Entity Framework.

The other thing is that we are also using C# and not VB on them.
Not that that is an issue...

We are currently using the option to build it from the database
and not even trying to build it in the designer. If your DB is
done correctly with all the foreign key relationships setup,
you will get a good entity model to work from.

The reason we stopped using nettiers was because it is a black
box that we cannot control. Entity framework and Linq to Objects
seemed to be the right way to go to keep everything internal
and not use 3rd party black box software that generated a massive
data layer. Although nettiers is a good product and worked well
on the application is it being used for.


At 12:00 PM 4/27/2009, you wrote:
>Date: Mon, 27 Apr 2009 17:27:32 +1000
>From: "Michael Maddison" <michael at ddisolutions.com.au>
>Subject: Re: [dba-VB] ADO.NET Entity Framework - to use or not?
>To: "Discussion concerning Visual Basic and related programming
>         issues."        <dba-vb at databaseadvisors.com>
>Message-ID: <59A61174B1F5B54B97FD4ADDE71E7D014F6957 at ddi-01.DDI.local>
>Content-Type: text/plain;       charset="us-ascii"
>
>Don't mean to intrude, but are you looking for something like
>http://www.nettiers.com ?
>We've used it in several projects, but not the one we are working on
>now.
>It works pretty damn well IMO.
>
>Cheers
>
>Michael M
>
>Date: Mon, 27 Apr 2009 13:50:15 +0400
>From: Salakhetdinov Shamil <mcp2004 at mail.ru>
>Subject: Re: [dba-VB] ADO.NET Entity Framework - to use or not?
>To: "Discussion concerning Visual Basic and related programming
>         issues."        <dba-vb at databaseadvisors.com>
>Message-ID: <E1LyNTb-0006Kd-00.mcp2004-mail-ru at f229.mail.ru>
>Content-Type: text/plain; charset=koi8-r
>
>Hi Michael,
>
>Thank you for your feedback.
>
>In my opinion we're looking for the ways to avoid using custom tools 
>as .netTiers, CSLA.NET, own custom frameworks (I have got developed 
>one like .netTiers, maybe with not that much features but rather 
>similar AFAIS - my own also works pretty well in real life apps) - 
>the main current "killer" framework to try is MS ADO.NET Entity 
>Framework, which is supported by .NET Framework SP1 (VS2008 SP1), 
>but which have some limitations e.g. absense of flexible SPs mapping 
>features (which BTW is not looking as an issue at all to Gustav :) 
>maybe for me only in our SCRUM team) but all(?) that limitations are 
>planned to be fixed in VS2010...
>
>Thank you.
>
>--
>Shamil