GregCSharp wrote:
Let me ask this: what is there is a TypedList named "CustomerOrders" in the LLBLGen project. I then create a table with the same name in the database and update my project?
When you sync from database it will fetch that information, that is: it will be available in the Catalog Explorer, no conflicts there, as those represents objects in your database.
When you do Reverse engineer to Entities from the Catalog Explorer, the Designer won't allow you to add it with the same name as an existing object in the group (Entity, TypedList, etc). Actually it will suggest you another name CustomerOrders1.
So, in short: choose another name
GregCSharp wrote:
I think this is where it started and where I lost track of that specific TypedList in v2.6.
I think there is room for an improvement there: since v3.x, as the grouping mechanism was introduced, the validation system checks for duplicates within groups, so no duplicate elements are allowed. In v2.6 this was not an issue, as there was not grouping mechanism.
However, the LLBLGen 2.6 Desinger with v4x templates generates a valid v4.x project which have duplicates elements (i.e. entity Order and typed list Order), if you validate this v4.x project, it will successfully pass designer validations.
So maybe there is room for improvement in the migration templates, or in the validation process, taking in account v2.6 migrated projects. We will look into it...