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
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 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