Is it easier to go from LinqToSQL to EF4.0 or EF3.5 to EF4.0?

views:

113

answers:

Is it easier to go from LinqToSQL to EF4.0 or EF3.5 to EF4.0?

Now that Entity Framework 4.0 is coming out I was wondering, if you were planning to use EF 4.0 when it is released would it be easier to go from LinqToSQL to EF 4.0 or EF 3.5 to 4.0?

In other words if you were starting a project now anticipating using EF4.0 would you use LinqToSQL or EF3.5 now?

+3 A:

It will be easier to migrate from EF 3.5, because many parts of the code will be common. It still will be a lot to do, because if I migrated to EF 4.0, I would propably switch to code only design. Why do you limit yourself to EF and Linq to SQL? There are other solutions: Subsonic, nHibernate. They are more mature, thought through and well tested.

LukLed 2009-11-24 08:40:29

Thanks for the reply. The reason I limit to LinqToSQL and EF is just because they do what I need and are built into the .net framework.

metanaito 2009-11-24 09:12:54

I wouldn't use it just because it is built into .net framework. LinqToSQL got many positive reactions, EF much, much less. You should at least look at other solutions.

LukLed 2009-11-24 18:43:51

Yes, I did consider others including Subsonic. LinqToSQL and EF for me just work, so I use them. I tried Subsonic a little but didn't have a great time setting it up (seems easy, but I ran into lot of errors). I've also had many experiences using 3rd party libraries that failed to keep up with the .net frameworks suddenly stopped being developed.I'm going to try EF4.0 before I make any decisions of course.

metanaito 2009-11-25 16:39:25

ansaurus

tags:

views:

answers:

Is it easier to go from LinqToSQL to EF4.0 or EF3.5 to EF4.0?

related questions