I migrated my code from v2.6 to v5.4. There was 2 TypedList might or might not have been remove the proper way from v2.6 project. Now in v5.4 project file, I am trying to create a new TypedList with the same name to match what my C# code expects.

I get an error saying the name is already in use in group '' I am attaching a scree shot just to demonstrate the issue.

Is there a way to manually remove in config file all traces of the previous typedlist to really startfrom scratch?

Thank you Greg

Is there an entity / typed view with that name in your project?

There was one file .cs not included in the project which i got rid off. But still no luck.

I also just noticed that I also have a table named by the name i am trying to use for this new typedlist, Could it be source of the conflict?

I also just noticed that I also have a table named by the name i am trying to use for this new typedlist, Could it be source of the conflict?

That's it indeed. (an entity is named after it and therefore the name you want to give to the new typed list clashes with it)

So that explains

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?

I think this is where it started and where I lost track of that specific TypedList in v2.6.

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...

Hi Daelmo,

I think my v2.6 project was kind of messed up before the migration already. I am not sure the issue came from the migration itself. I would not look into this unless you have other feedback on that.

Thanks for the support anyway!

Thanks. We will evaluate it anyway in order to improve in that area, if possible. Thanks for reporting this.