One more issue is writing 'connection strings' to connect and disconnect from database. Thus developer is spending too much time on database related issues. The real aim of developing application logic is delayed.  ADO.NET Entity Framework along with LINQ tries to address these issues making application development simple and quick.

ADO.NET Data Service

We are moving away from application that are tightly coupled with programming language and operating system towards architecture that allows development of application (on different platforms) to communicate with each other. Now moving on same line VS 2008 SP1 is integrated with ADO.NET Data Service for making data available as service.

To create EDM of the 'School' data base click on 'Project > Add New Item', from the list select 'ADO.NET Entity Data Model' and change name to 'School.edmx'

Data as service can make data usage more flexible. Here let me explain how data as service can be used; consider a school where attendance is taken using punch cards (based on RFID). Now once students enter school data collected using punch card is fed in database. If the same data is made available to parents using ADO.NET Data Service over web. Parents can easily track their children. This data can also be made available on mobile devices further simplifying on demand data access.

ASP.NET Dynamic Data

This feature simplifies building of data driven application based on a LINQ to SQL or Entity Framework data model. One added feature of ASP.NET Dynamic Data is enhanced functionality of the FormView, DetailsView, GridView, and ListView controls. 

Besides these features other features to look out in this release include: ADO.NET AJAX Browsing history that helps in navigation within AJAX application using forward and back button of browser. ADO.NET script combing feature for improving performance of AJAX application by reducing script download.