Firebird in Designer 5.0

Posts   
 
    
Posts: 256
Joined: 05-Jul-2010
# Posted on: 16-Nov-2016 12:39:34   

Hi

I have some difficulties getting the firebird provider up and running in the designer. I don't want to install the provider in the gac. I tried the latest version of the provider and the one that worked for the 4.2 designer. I know I'm forgetting something obvious, but it is obvious that I don't know what.

thanks

Alexander


Exception type: ArgumentException Unable to find the requested .Net Framework Data Provider. It may not be installed.

Posts: 256
Joined: 05-Jul-2010
# Posted on: 16-Nov-2016 15:47:16   

Ok solved, just edited the config file again.

thanks

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 17-Nov-2016 10:43:01   

To my knowledge the Firebird ADO.NET provider developer has created an installer which installs the factory in the machine.config as well, so editing a config file shouldn't be necessary. Did you use the installer?

Frans Bouma | Lead developer LLBLGen Pro
Posts: 256
Joined: 05-Jul-2010
# Posted on: 17-Nov-2016 10:44:27   

Otis wrote:

To my knowledge the Firebird ADO.NET provider developer has created an installer which installs the factory in the machine.config as well, so editing a config file shouldn't be necessary. Did you use the installer?

Hi

No, never, I use nuget to get my providers and I don't install it.

thanks

a

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 17-Nov-2016 10:50:14   

Alexander wrote:

Otis wrote:

To my knowledge the Firebird ADO.NET provider developer has created an installer which installs the factory in the machine.config as well, so editing a config file shouldn't be necessary. Did you use the installer?

Hi

No, never, I use nuget to get my providers and I don't install it.

thanks

a

Ah, then you indeed need to change the config simple_smile

Frans Bouma | Lead developer LLBLGen Pro
Posts: 256
Joined: 05-Jul-2010
# Posted on: 17-Nov-2016 10:53:16   

Otis wrote:

Alexander wrote:

Otis wrote:

To my knowledge the Firebird ADO.NET provider developer has created an installer which installs the factory in the machine.config as well, so editing a config file shouldn't be necessary. Did you use the installer?

Hi

No, never, I use nuget to get my providers and I don't install it.

thanks

a

Ah, then you indeed need to change the config simple_smile

Yeh, would you mind changing the remark in your config file. I was planning to change it, but then I saw your message and decided not to do it. I think by now more people are using nuget for firebird. On the other hand... maybe I'm the only guy using it in combination with llblgen.

thanks anyway

5 looks good.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 17-Nov-2016 11:09:08   

Alexander wrote:

Otis wrote:

Alexander wrote:

Otis wrote:

To my knowledge the Firebird ADO.NET provider developer has created an installer which installs the factory in the machine.config as well, so editing a config file shouldn't be necessary. Did you use the installer?

Hi

No, never, I use nuget to get my providers and I don't install it.

thanks

a

Ah, then you indeed need to change the config simple_smile

Yeh, would you mind changing the remark in your config file. I was planning to change it, but then I saw your message and decided not to do it. I think by now more people are using nuget for firebird. On the other hand... maybe I'm the only guy using it in combination with llblgen.

You're not the only one using it with firebird simple_smile although firebird isn't that widely used.

It's the same as with postgresql: people download the ado.net provider from nuget. This is understandable, however it's not necessary: with referencing the provider from nuget the dependency becomes direct, while the dependency is indirect (through dbproviderfactory). This means that if the ado.net provider updates, your code has to update too (recompile), which isn't needed.

IMHO the best way is to simply run the installer to install the ADO.NET provider and not use nuget in this case as you're not using the ado.net provider directly. This gives you the opportunity to update the ado.net provider without a necessary recompile of your code.

For deployment you can then either decide to run the installer when you deploy, or ship the dll with your application and register the factory in your application's config file.

5 looks good.

Thanks simple_smile

Frans Bouma | Lead developer LLBLGen Pro
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 28-Nov-2016 10:44:23   

updated in next build

Frans Bouma | Lead developer LLBLGen Pro