Entity Developer for SQL Server can create LINQ to SQL (not LinqConnect) models for your applications. However LINQ to SQL and LinqConnect have much common functionality, and most of the documentation about LinqConnect models, applicable to the LINQ to SQL models. This topic describes the main differences in using Entity Developer for LINQ to SQL and LinqConnect models.
LINQ to SQL models can be created for SQL Server only. You may choose only .NET Framework Data Provider for SQL Server or .NET Framework Data Provider for Microsoft SQL Server Compact only for the model connection.
Complex Types
LINQ to SQL model supports complex types only as a return type for the methods. It does not support entity properties of a complex type. There are no complex types on a LINQ to SQL diagram or in the model explorer, however you still can create them using the method editor and use them as the return types of the methods. |
Associations
LinqConnect supports Many-to-many associations, while LINQ to SQL doesn't. That causes differences in the Association Editor and association properties. |
Columns
LinqConnect supports Identity generation which is not supported by LINQ to SQL. LinqConnect columns have IdGenerator property, which is not present in LINQ to SQL models. |