Skip to main content

Not ready for Entity Framework? Then What?

Will Smith and I started an offline thread based on his post "Uninstalling EF Beta 3". Granted, the ADO.Net Entity Framework is still beta and probably won't go gold until Summer, but I wondered what he would use instead. His team is solid but not advanced and he wants to keep complexity to a minimum while remaining as agile as possible. Here's my advice. Your thoughts?
You're probably wise in steering away from 3.5 stuff with an uninitiated staff. I'd probably encapsulate your data access leveraging the Enterprise Library Data Access Application Blocks. You could leverage CodeSmith and NetTiers to quickly generate the data access layer effectively shielding your less-advanced developers from the complexity (they simply call class library methods vs. code ADO.Net 2.0). Later, when you want to shift to ADO.Net Entity Framework or [less likely] LINQ to SQL, you can rip out this data access layer simply replacing it with EF or LINQ. Granted, [obviously] you'll have to adjust the consuming classes to leverage LINQ afterwards but it should be a less-invasive change.

Update: 3/4/2008: Related, I'm recommending the Repository Factory guidance pattern. From the site:
The Repository Factory is a guidance package that automates creation of entity classes that map to database tables and repository classes to read and write those entity classes. The generated code removes the tedium of writing a persistence-ignorant domain model.

This package was originally published as the "Data Access Guidance Package" as part of the Web Service Software Factory. Data access is a much larger problem space than just services, so we've decided to split this package out into its own project.

Comments

Popular posts from this blog

Starting a New Blog with my Cousin

On 9/15/2006, my cousin (he's really a 2nd cousin many times removed...I'm not convinced we're actually related ;-) John Ingrisano and I will launch a new blog targeted to the small business owner. He'll provide most of the content and I will provide the technical and marketing expertise. Ok, ok, starting a blog isn't rocket science but we're aiming to [eventually] derive some sort of profit from this venture, so I plan on doing this right. The two blogs I currently maintain live on the free Blogger.com and LiveJournal.com. I'll be covering the adventure here on Effective Thoughts--providing insight as to what worked and what didn't. To start off, our first activities are: Choose a name and a theme Find a host Help John learn the ins and outs of blogging Implement the site: look/feel, about/bio, 1st content, announcements, etc. Understand marketing best practices To this end, here is some research I compiled: Finding a host http://en...

Switching the Parents to Ubuntu...?

I spent a half hour or so recently on the phone walking my Mom through a technical issue. Tentatively, I diagnosed her issue as a hard drive failure. She brought it over on her last visit and sure enough, the Dell XPS 450 from circa 1999 sounds like a bad coin-operated laundry at full capacity. I was aghast to discover she's running Windows 98. Ugh. Also, her recovery disk is just that--for recovery. I don't believe I'll be able to re-install Win98 on a new hard drive. That, coupled with the end of Microsoft (and Dell) support for Win98, got me thinking about Linux. (and she's not intense about her computing needs...and she doesn't want to spend much money...) I've been reading good things about switching one's parents to Ubuntu. Any thoughts out there?