I had a llblgen pro 2.5 (final) project that used a custom TypeConverter that I had implemented. I recently changed my db and, as a result, I don't need the type converter any more for any of the entities in my project.

In the designer I clicked Project | Edit Type Conversion Definitions... and I deleted my type converter.

I then went to the four fields where I had been using this type converter to make sure it was still being used. It wasn't.

I regenerated but the generated code still insisted on using the type conversion. In PersistenceInfoProvider.cs there is a method named InitOutputEntityMappings(). In it are calls to base.AddElementMapping. One of the parameters to those calls was a newly-created TypeConverter of the type that USED TO BE associated with the entity field in question.

I work around the issue by hand-editing PersistenceInfoProvider.cs to replace those parameters will "null".

The designer seems to not want to forget my old type converter. How do I make it forget!

I am generating adapter code usign LLBLGen Pro 2.5 Final. Target is .NET 2.0 C#. Database is SQL Server 2005. SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll version is 2.5.0.0.

Please make sure the file PersistenceInfoprovider is overwritten during code generation. Also, make sure that the db specific project is indeed up to date in your application's bin folder.

Yes, PersistenceInfoProvider.cs is being overwritten. I have to hand edit it after every time that I do a Generate.

I just double-checked my Project | Edit Type Conversion Definitions... dialogue - nothing listed in there.

As for the db specific DLL, after I hand-edit the PersistenceInfoProvider.cs so that I can successfully rebuild that application, it certainly gets updated in the application's bin folder.

Could you open a helpdesk thread and attach your project to a post there so we can have a look? I can also move this thread to that forum so you can attach it to this thread after that.

Thread continued in helpdesk.