Fixed the conflicts of the definitions and ambiguity between DBML
and EDMX
design. Renamed the class names of DBML
as TABLEONE_DBML
and it worked well for EDMX
.
Using ADO.NET Linq to Sql and Entity Data Model in same Project causes Naming instances errors
-
15-07-2023 - |
Вопрос
I am using ADO.NET LinqtoSql for populating data into SqlDatabase tables after parsing from flat files using LINQ. I am also using an Entity Data Model in the same project for displaying those Populated SqlDatabase tables in a JQGrid.
Entity Data Model is used to select datasets from multiple columns from multiple SqlDatabase tables using LINQ.
Exceptions and Errors obtained:
Ambiguity between 'TABLE.TABLEONE.FileCreated' and 'TABLE.TABLEONE.FileCreated'
The type 'TABLE.TABLEONE' already contains a definition for 'Tableone_ID'
I am able to rectify these errors if the definitions declared in the ADO.NET Entity Model.edmx design are renamed to a different name.
How to resolve the exceptions without changing the definitions and proceed with our development. Help needed.
Решение
Не связан с StackOverflow