Oracle odp.net installer

Configuration and tracing registry values apply across all ODP. NET applications running in that Oracle client installation. Individual ODP. NET application itself for example, FetchSize. The ODP. There is one key for. NET Framework 1. NET Framework 2. For customers who have numerous applications on a computer that depends on a single version of ODP. To provide more granular control, ODP. NET configuration settings in an application config, web.

If a computer does not require granular control beyond configuration settings at the ODP. NET configuration settings through configuration files. The following is an example of a web. This assembly is only needed in your application if you use distributed transactions with. It is optional to use with. This assembly is only needed in your application if you are using Kerberos security. These two assemblies are not intended to be directly referenced by an application. Rather, they will be referenced implicitly.

NET, Managed Driver will reference these assemblies by using the following search order:. The web application's bin directory or Windows application's EXE directory. The x86 or x64 subdirectory based on whether the application runs in bit or bit. NET Framework. Oracle recommends using this method of finding dependent assemblies if your application is AnyCPU.

For example, use the following steps for your application to use the bit version of Oracle. To make your application platform independent even if it depends on Oracle. In an Oracle Universal Installer based install, the Oracle. Oracle recommends using this method of finding dependent assemblies if your application is AnyCPU. For example, use the following steps for your application to use the bit version of Oracle.

To make your application platform independent even if it depends on Oracle. In an Oracle Universal Installer based install, the Oracle. Documentation and the readme. Previous Next JavaScript must be enabled to correctly display this content. Run the configure. NET, Managed Driver will reference the assemblies by using the following search order: Global Assembly Cache The web application's bin directory or Windows application's EXE directory The x86 or x64 subdirectory based on whether the application runs in bit or bit.

For x86 targeted applications, name the folder x86 and add the assembly from the x86 directory. NET provider.