Dattatray's space

 

I have successfully Implemented Openbravo ERP for the Mid-size manufacturing Industry. 

 

Openbravo ERP is bundle of the following module.

 

1.Finnace

2.Procurement.

3.Sales & Services.

4.Warehouse Management.

5.Production Management.

6.Project And Services.

and Most Core heart of any ERP module is MRP (Material Requisition Planning).

 

Using this functionality I have Implemented this for India customer.

 

Cheers,

 

 

 

 

 

I am confused that which is faster. I required to test some result Against the both the technology.

 

But during the R&D I found that LINQ to SQL is little bit faster

 

Cheers,

Below are the few difference between LINQ to SQL (dbml) and  Entity Framework (edmx)     Category	LINQ to SQL	Entity Framework
Model	domain model	conceptual data model
Databases Supported	as the name indicates: SQL server only	variety of databases
Data Sources	tables only	tables, replication, reporting Services, BI and etc
Complexity	simple to use	complex to use
Development Time	rapid development	slower development but more capabilities
Mapping	class to single table	class to multiple tables
Inheritance	hard to apply	simple to apply
File Types	dbml files only	edmx files after compilation generate 3 xml files to represent the schema: csdl, msl and ssdl

 

Today Morning I tried to create Entity Designer (*.edmx) using wizard.

 

I got above error message which is mentioned in the subject line. For more detail we can check below link.

 

 

I tried to Map the table who has Pimary Key. Now funny thing is that the error was gone.

 

Then I realize that If you don't have the Primary key then It gives above error

 

Solution : (work around) Primary Key in the database table !

 

 

Cheers

 

When Do I Use LINQ to SQL?

The primary scenario for using LINQ to SQL is when building applications with a rapid development cycle and a simple one-to-one object to relational mapping against the Microsoft SQL Server family of databases. In other words, when building an application whose object model is structured very similarly to the existing database structure, or when a database for the application does not yet exist and there is no predisposition against creating a database schema that mirrors the object model; you can use LINQ to SQL to map a subset of tables directly to classes, with the required columns from each table represented as properties on the corresponding class.

When do I use LINQ to Entities?

The primary scenario targeted by LINQ to Entities is a flexible and more complex mapping scenario, often seen in the enterprise, where the application is accessing data stored in Microsoft SQL Server or other-third party databases.

The Future of LINQ to SQL :

ADO.net Team, which is supporting both LINQ to SQL and Entity Framework, made some clear statement. It is now clear that as of .NET 4.0, LINQ to Entities will be the recommended data access solution for LINQ to relational scenarios (Published Thursday, November 06, 2008 4:29 PM by kcasada)

 

Enjoy Coding with LINQ.

Thanks

DDPatil