I'm running into this error while opening my project in the newly installed v5.10.1 (not 10.5.1 as in the title :-) )

Exception information.
=============================================================
LLBLGen Pro version: v5.10. Build: 5.10.1

Exception details:
=====================
Message: The XML contains a reference to a driver with ID: '2D18D138-1DD2-467E-86CC-4838250611AE' which isn't loaded, likely due to a missing ADO.NET provider. Line 1594, Position 6
Source: SD.LLBLGen.Pro.ApplicationCore
Stack trace: 
   at SD.LLBLGen.Pro.ApplicationCore.MetaData.MetaDataStore.DeserializeTargetDatabase(XmlReader reader)
   at SD.LLBLGen.Pro.ApplicationCore.MetaData.MetaDataStore.DeserializeFromReader(XmlReader reader)
   at SD.LLBLGen.Pro.ApplicationCore.ProjectClasses.Project.DeserializeFromFile(String filename, String additionalTypeConverterFolder)
   at SD.LLBLGen.Pro.ApplicationCore.ProjectClasses.Project.Load(String filename, String additionalTypeConverterFolder)
   at SD.LLBLGen.Pro.Gui.Classes.GuiController.PerformOpenProjectAction(String filenameToOpen)

Inner exception: <null>

The line in the XML in question:

    <TargetDatabase Type="2D18D138-1DD2-467E-86CC-4838250611AE" SyncSource="2">

Any idea what is happening?

EDIT Might it be related to the fact that, when creating a new, empty project, Db first, I do not have any Providers in the Database provider dropdown?

That's strange. The 2D18... is sql server, it should be there in the .NET 4.8 installation. Could you check the machine.config file in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config to see if there are DbProviderFactory descriptions there? Also, did you by accident start the 32bit version perhaps?

Otis wrote:

Could you check the machine.config ... to see if there are DbProviderFactory descriptions there?

No, no occurrence of the word "DbProviderFactory" in machine.config

Otis wrote:

Also, did you by accident start the 32bit version perhaps?

No, right after installation I started the 64bit version of v5.10.1. However, my previous (still) installed version 5.9.2, I always had/have to start in 32bit, due to a similar issue. Similar in the sense of also issue with Sql provider.

Come to think of it. I'm having issues with Sql provider each time I'm installing a new version :-)

Checking the config file myself I remember the sql server provider is auto-added to the DbProviderFactories class by the class itself in netfx so it's not defined in the machine.config file. It might be good to check whether the .NET 4.8.x installation is OK. In the visual studio installer, for 2022, click Modify and then check if you have the .NET Desktop development workload checked. if not, please check it so it can install (or repair) .net 4.8

The 32bit version is only needed for older oracle installations, you always should use the 64bit version

Otis wrote:

check if you have the .NET Desktop development workload checked.

It was not, but .NET Development tools where installed. But ok, I installed the entire Desktop development toolset. That did not fix it.

Then I downloaded and repaired the .NET Framework 4.8 Developer Pack. Still no luck.

I double checked: I can open the project in v5.9.2 but not in v5.10.1. Strange no? As I guess the provider-detection mechanisme is not changed?

When creating a new project, db first, the v5.9.2 give me a dropdown with all the providers. That dropdown is empty in v5.10.1.

I double checked: I can open the project in v5.9.2

Is this the x64 version, or still the x32 that's working?

After repairing and installing .NET SDK, could you please re-install v.5.10 of LLBLGen Pro.

I managed to fix it, using v5.10.0.

Here is the story. It's up to you to conclude if there is an issue with installer(s)

I reinstalled v5.10.1. Same issue. I rebooted pc. v5.9.2 - 64bit is working. v5.10.1 is not.

But hey, this is weird: I do not have any "Solutions Design" folder in my "C:\Program Files\" !!?

And indeed, all shortcuts made by the installed are pointing to the only LLBLGenPro.exe on my system, which are under the "C:\Program Files (x86)\Solutions Design\" folder. (not 100% sure about the target exe anymore, as I now know there is a _x86.exe)

So I uninstalled the two versions of LLBLgen from my system.

Cleaned up the registry to be sure.

Reinstalled v5.10.1 where I made sure that the "C:\Program Files\" folder was being used (indeed, it suggested the x86 folder)

Result:

• LLBLGenPro.exe is installed in the 64bit folder, but not in 32bit folder.
• The shortcuts are reversed (32bit pointing to programfiles, 64bit pointing to x86 folder).

Uninstall again, and this time installed v5.10.0. Suggested install folder was still x86. Changed that to "C:\Program Files\". And this time I did not install VS extension.

Result:

• LLBLGenPro.exe is installed in the 64bit folder, but not in 32bit folder. (as by design as I understand it now)
• Shortcuts both point to "C:\Program Files\". Target exe is different; 32bit points to its own _86.exe.

So, some weird stuff going on with only two variables:

• the v5.10.0 versus v5.10.1 installer
• installing VS extension yes or no. So not sure which of those is key. But for me: case closed.

Thx for your swift responses. Much appreciated!

rsiera wrote:

I managed to fix it, using v5.10.0. Here is the story. It's up to you to conclude if there is an issue with installer(s)

I reinstalled v5.10.1. Same issue. I rebooted pc. v5.9.2 - 64bit is working. v5.10.1 is not.

But hey, this is weird: I do not have any "Solutions Design" folder in my "C:\Program Files\" !!?

That's expected, the files install in program files (x86)\Solution design. They're (all cpu) and will thus run 64bit, but we install in that folder for decades now so we kept it. It's the 64bit version. We ship a 32bit runner with it, which will forcefully make the designer run in 32bit. Running the LLBLGenPro.exe will run the 64bit version.

And indeed, all shortcuts made by the installed are pointing to the only LLBLGenPro.exe on my system, which are under the "C:\Program Files (x86)\Solutions Design\" folder. (not 100% sure about the target exe anymore, as I now know there is a _x86.exe)

So I uninstalled the two versions of LLBLgen from my system.

Cleaned up the registry to be sure.

Reinstalled v5.10.1 where I made sure that the "C:\Program Files\" folder was being used (indeed, it suggested the x86 folder)

Result:

• LLBLGenPro.exe is installed in the 64bit folder, but not in 32bit folder.
• The shortcuts are reversed (32bit pointing to programfiles, 64bit pointing to x86 folder).

Uninstall again, and this time installed v5.10.0. Suggested install folder was still x86. Changed that to "C:\Program Files\". And this time I did not install VS extension.

Result:

• LLBLGenPro.exe is installed in the 64bit folder, but not in 32bit folder. (as by design as I understand it now)
• Shortcuts both point to "C:\Program Files\". Target exe is different; 32bit points to its own _86.exe.

So, some weird stuff going on with only two variables:

• the v5.10.0 versus v5.10.1 installer
• installing VS extension yes or no.

The 5.10.0 and 1 installer are the same script (as is the 5.9 installer), so it's weird it doesn't work. We'll double check tho. The vs extension isn't influencing this, the extension is merely a wrapper around the designer.

So not sure which of those is key. But for me: case closed.

Not sure I follow Reading the above, you still can't open / load a project in 5.10.1, right? So we need to get to the bottom of that as you should be able to work normally.

Otis wrote:

Not sure I follow Reading the above, you still can't open / load a project in 5.10.1, right?

Yes that right, well, maybe... I haven't tried anymore. I'm now using v5.10.0 so I'm happy :-) I'm going to tackle other items of my todo list now. Upgrading to 5.10.1 or later, and making sure I'm using the default x86 folder again, that's for later. Unless you would advise otherwise, because of the hotfix nature of 5.10.1.

The installation folder shouldn't matter with respect to which dbproviderfactories are visible. 5.10.1 has a change in the runtime, the designer is the same. The installer script is literally the same script used for 5.10 as for 5.10.1 So it's weird that one works and one doesn't....

Installing 5.10.1 in program files\solutions design\llblgen pro v5.10 indeed reproduces it! We'll look into this.

(edit) installing it in the default folder also fails. Bizarre!

(edit) we found it, the drivers weren't properly built with the new version number. We fixed an issue in the runtime, we pushed a hotfix build but forgot to change the version to 5.10.1, so we did that, rebuild the runtime and rebuild designer and the installer (but forgot to do a full rebuild with drivers), so the drivers weren't properly build. We'll upload a new installer

We fixed it, the installer for hotfix build v5.10.1 should work now, no matter where you install it

Yes, much better!