Upgrading to Entity Framework from Linq to SQL
Although I have been through a number of posts that discuss Linq to SQL and Entity Framework there still exists a lot of confusion at this stage about the following questions.

Before I mention the questions let me say that I have completed a desktop application using Linq to SQL and this usage is based purely on mapping and using SPROCS. 

1. Do I need to upgrade or rewrite my CRUD operations to using Entity Framework? If so what are the advantages that I will have using entity framework over Linq to SQL with SPROCS?

2. Is Entity framework supported by Visual Studio 2008 / .net framework 3.5? 

3. What are the differences between Entity Framework support in .net 3.5 and 4.0?

These are just a few of the questions that I need some help with before I form a complete picture of the scenario.

If any of you out there have any useful insights that you can provide I would appreciate it

Thanks a ton in advance




Upgrading to Entity Framework from Linq to SQL
===

Although I have been through a number of posts that discuss Linq to SQL and Entity Framework there still exists a lot of confusion at this stage about the following questions.

Before I mention the questions let me say that I have completed a desktop application using Linq to SQL and this usage is based purely on mapping and using SPROCS. 

1. Do I need to upgrade or rewrite my CRUD operations to using Entity Framework? If so what are the advantages that I will have using entity framework over Linq to SQL with SPROCS?

2. Is Entity framework supported by Visual Studio 2008 / .net framework 3.5? 

3. What are the differences between Entity Framework support in .net 3.5 and 4.0?

These are just a few of the questions that I need some help with before I form a complete picture of the scenario.

If any of you out there have any useful insights that you can provide I would appreciate it

Thanks a ton in advance



