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

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

Up vote 1 down vote favorite share g+ share fb share tw.

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! Linq-to-sql entity-framework linq-to-entities sql-azure link|improve this question edited Apr 20 '10 at 3:19 asked Apr 20 '10 at 3:08Craig L475 50% accept rate.

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.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.