Skip to Main Content

ODP.NET

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

DbProviderFactories and machine.config

user8960976Aug 15 2012 — edited Aug 16 2012
When are the Oracle.DataAccess.Client registred as a DbProviderFactory in the machine.config?
I'm seeing different behaviours after installing opd.net which is a real pain when deploying binaries.

I have 2 different machines, and here I list where the dll is registered.

machine 1 : ODP 32bit 2.111.7.0
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config (only)

machine 2 : ODP 32bit + 64bit 11.2.0 (2 installations)
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config
C:\Windows\Microsoft.NET\Framework\v4.0.30319\CONFIG\machine.config
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config
C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config

The problem is that if it is not registred in the machine.config it must be registered in the app.config. But it cannot be both.

This is painfull when building releases that should target different machines.

Why does a ODP 32bit change the 64bit machine.config only?
How should this be handled?
Should i manually update the unregistred machine.config?

Thanks

Edited by: user8960976 on 2012-08-15 06:29

Edited by: user8960976 on 2012-08-15 06:30
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Sep 13 2012
Added on Aug 15 2012
2 comments
3,623 views