What is the difference between .edmx and .dbml file in linq?

Question

What is the difference between .edmx and .dbml file in linq? In VS 2008, which data source is the best choice, where is edmx or dbml? Any problem arising using edmx file in VS 2008? Can i use edmx in VS-2008?

Answer 1

edmx is a simulation file for the Entity Framework .

dbml is a simulation file for Linq 2 Sql .

You should spend your time learning the Entity Framework since Linq 2 Sql is deprecated.

Answer 2

.edmx is the Entity Framework. .dbml is LINQ-to-SQL. Although their common goal is the same, they represent a completely different framework. The Entity Framework is newer and is likely to be the best investment of your time to learn, since I suspect there will be a lot of innovation.

Answer 3

Both of them are presented as the latest technology, and sometimes a little confusing when to use them. Entity Framework and LINQ to SQL have much in common, but still differ from each other in several ways:

Entity Framework:
1. Enterprise development:
2. Works with a conceptual database model:
3. Works with all data sources:
4. ".EDMX" is created using the Entity Framework:

LINQ ::
1. Rapid application development:
2. Work with objects in the database:
3. Basically woks with SQL Server:
4. ".dbml" is created using LINQ to SQL:
:

The Entity Framework is more focused on Enterprise Development, where the scheme is usually optimized for storage considerations such as performance consistency and partitioning. The Entity Framework is designed around the disclosure of an application-oriented data model that is loosely coupled and may differ from the existing database schema. For example, you can map one object (class) to several or map several objects in one table. Entity Framework has a .edmx file (ADO.NET Entity Model) when added to the application.

LINQ to SQL mainly has support features for rapid application development for SQL Server. LINQ to SQL allows you to have a strongly typed view of your existing database schema. You can create LINQ queries on tables and return results as strong typed objects. LINQ to SQL has a ".dbml" (LINQ to SQL) file when added to the application. You can use LINQ to SQL by decorating existing classes with attributes.

Answer 4

LINQ to SQL mainly has support features for rapid application development for SQL Server. LINQ to SQL allows you to have a strongly typed view of your existing database schema. You can create LINQ queries on tables and return results as strong typed objects. LINQ to SQL has a ".dbml" (LINQ to SQL) file when added to the application. You can use LINQ to SQL by decorating existing classes with attributes.

Answer 5

I never understood literature as definitions. In any case, the bottom line of L2S is light, and EF is heavy. L2S only works with SQLServer and EF works with many others.

Reference: The difference between L2S and EF