LINQ to SQL vs Entity Framework for an app with a future SQL Azure version

Question

I've got a vertical market Dot Net Framework 1.1 C#/WinForms/SQL Server 2000 application. Currently it uses ADO.Net and Microsoft's SQLHelper for CRUD operations.

I've successfully converted it to Dot Net Framework 4 C#/WinForms/ SQL Server 2008. What I'd like to do is also offer my customers the OPTION to use SQL Azure as a backend storage for their data instead of local/LAN SQL Server.

If I know SQL Azure is in my application's future, should I:

A. Switch to LINQ to SQL

or

B. Swith to Entity Framework

or

C. Stick with ADO.Net and SQLHelper

?

Thanks !

Sam Saffron · Accepted Answer · 2010-05-05 23:21:38Z

1

I would switch to Entity Framework, it works just fine with SQLAzure and is the recommended ORM by Microsoft for .Net 4

answered May 5, 2010 at 23:21

Sam Saffron

132k81 gold badges336 silver badges511 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Rabbi · Accepted Answer · 2010-05-07 16:29:59Z

0

ADO.net works just fine,

My personal favorite is Linq2Sql which works fine with azure

Microsoft is now recommending that everyone switch to entity framework

answered May 7, 2010 at 16:29

Rabbi

4,7529 gold badges40 silver badges48 bronze badges

Collectives™ on Stack Overflow

LINQ to SQL vs Entity Framework for an app with a future SQL Azure version

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related