Hi,

I have to upgrade and old LLBLgen website to dotnet 4.8. I am using LLBLGen 5.8 in Visual Studio 2019 and the sources come from Visual Studio 2013. I am using SelfServicing.

When I open a webpage in VS it shows the following kind of message where a LLBLGenProDataSource is used:

Error Creating Control - _potentieleTypesDS'HITc.WBS.CollectionClasses.TypeCollection, HITc.WBS' could not be set on property 'EntityCollectionTypeName'.

When I try to reassing the collection to the LLBLGenProDataSource controle via the configuration arrow, it shows an empty list. It does not seem to see the available LLBLGen datasources.

How can I make this work?

Thanks, Jan

Could you close vs, delete the .vs folder (hidden in the solution folder) and then restart vs to see if the gui at least works now? You didn't change anything else besides migrating to .net 4.8?

No, I did not change anything else. I have been having problems with the LLBLGenProDataSource since 2009 or so. It was so anoying that I stopped using them and started doing all databinding stuff in source code. Now I have to work on code that is pre 2009 and the problems occur again.

Deleting the .vs file did not have any effect.

I am not upgrading the old asp.net web project but I am taking over the old .aspx files in the new asp.net project. Then I alter the master page and try to make the code work with the new data definitions.

The first time I tries this with a page that has a LLBLGenProDataSource I had the impression that the LLBLGenProDateSource was working ok. I was able to select a new dataset using the configuration proces. Trying it again the next day and it would no longer function.

At the moment the code does function if I manualy fill in the EntityCollectionTypeName.

Kind regards,

Jan

Yeah don't get me started on these datasource controls... writing them was such a pain, the whole feature in ASP.NET is broken, or at least, it's very cumbersome to work with. It works when setting it up in code/html, but the design time experience is ... terrible. I have never figured out what might cause the issues tho, as it sometimes works and sometimes it doesn't...

So I guess it will not be solved. I'll work around it.

Sadly, no, there's nothing we can do about this, dare I say it, shit behavior in the design part of this control. I'm sorry.