Difference between Linq to SQL and the ADO.NET Entity Data Model and which one should be useful in future???

Difference between Linq to SQL and the ADO.NET Entity Data Model

LINQ to SQL supports rapid development of applications that query Microsoft SQL Server databases using objects that map directly to SQL Server schemas.  LINQ to Entities supports more flexible mapping of objects to Microsoft SQL Server and other relational databases through extended ADO.NET Data Providers.

If you are writing an application that requires any of the following features, you should use the ADO.NET Entity Framework:

·         The ability to define more flexible mapping to existing relational schema, for example:

o   Mapping a single class to multiple tables

o   Mapping to different types of inheritance

o   Directly Modeling Many to Many relationships

o   Mapping to an arbitrary query against the store

·         The ability to query relational stores other than the Microsoft SQL Server family of products.

·         The ability to share a model across Replication, Reporting Services, BI, Integration Services, etc.

·         A full textual query language

·         The ability to query a conceptual model without materializing results as objects

If you do not require any of these features, LINQ to SQL may provide a simpler solution for rapid development. LINQ to SQL is targeted at rapid-development scenarios against Microsoft SQL Server and provides a simpler approach and richer design experience in the Orcas timeframe for applications with data classes that map directly to the schema of your Microsoft SQL Server database.