Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
4 posts • Page 1 of 1
We are using 'Installshield' to create MSI installer. There are ways to query the DB using the script support in 'InstallShield'. But that would require oracle client. So the motivation is to use 'dotconnect for Oracle' in direct mode to run queries during install. This is simple as long as the queries can be packaged in a managed dll(called custom action), which I see as no big deal. Now the real qn. is how do we set up the license for this custom action dll. Should the 'Licenses.config' file contain the Windows Installer executable 'Msiexec.exe' since it is the calling program that uses the dotconnect internally?
we'd like to use the Factory pattern for creating connections. Since we can't change the config file for MsiExec, I am hoping that having the following entry it in our assembly's config file will work. Please confirm.
The DbProviderFactories entry should be added either to machine.config or to app.config of the application; provider factories specified in the configuration file of the assembly will be ignored by the executable file. We can only recommend you to directly create Devart.Data.Oracle.OracleProviderFactory instead of using DbProviderFactories.GetFactory("Devart.Data.Oracle").