I have a very old codebase developed against the 2.6 version. Now on SQL Server 2019 I can't refresh the catalog so I could regenerate the code.
I ran into the issue with the 2.6 SQL Server driver not working against latest versions, so I updated the code to work against later versions and got it to run, but now it seems to hang when refreshing the catalog.
What's involved in upgrading to the 5.x version? Is this a major undertaking and how much will my runtime code be affected? Is there some documentation on the upgrade process?
As v2.6 is over 12 years old, a lot has changed. You very likely won't run into all the breaking changes but you will run into some of them. A lot of people have migrated to higher versions from v2.6 before you and have asked questions you might have too here so it's likely you'll find answers here by searching for them. If not let us know and we'll look into it.
I ran into the issue with the 2.6 SQL Server driver not working against latest versions, so I updated the code to work against later versions and got it to run...
Would you mind sharing what code you were able to update to get the 2.6 driver to work with SQL Server 2019? Did you somehow edit the actual code for the driver?
The changes are made to the LLBLGenProSDK, in the SqlServerCatalogRetriever.cs and SqlServerSchemaRetriever.cs files. Basically, I've added default cases to various switch statements to handle any version of SQL server not covered.
The built DLL then needs to be copied into the appropriate drivers folder for LLBLGen to access. This is in the following path on my system:
C:\Program Files (x86)\Solutions Design\LLBLGen Pro v2.6\Drivers\SqlServer
I've now also attached my built DLL to this post (pending approval).