ODP.NET Compatibility Regarding 32-bit vs 64-bit OS, Application and Provider
(Doc ID 761214.1)
Last updated on JULY 03, 2023
Applies to:
Oracle Data Provider for .NET - Version 9.2.0.8 and laterMicrosoft Windows (32-bit)
Microsoft Windows x64 (64-bit)
Microsoft Windows Itanium (64-bit)
Goal
Valid ODP.NET Configuations
When deploying an ODP.NET application across 32-bit vs. 64-bit environments the following configurations are valid.
Built On |
Deployed On | ||||
---|---|---|---|---|---|
OS |
Target CPU |
ODP.NET |
OS |
Runs As |
ODP.NET |
Windows 32-bit |
x86, AnyCPU |
32-bit |
Windows 32-bit |
32-bit |
32-bit |
Windows 32-bit |
x86 |
32-bit |
Windows 64-bit |
32-bit |
32-bit |
Windows 32-bit |
AnyCPU |
32-bit |
Windows 64-bit |
64-bit |
64-bit |
Windows 32-bit |
x64 |
32-bit |
Windows 64-bit |
64-bit |
64-bit |
If you are having problems with your configuration you can use the following information to trouble-shoot your environment.
Trouble-Shooting Your Environment
Depending on the following five factors...
- What bit version of the Windows OS did you build your application on?
- What bit version of the Windows OS do you want your application deployed on?
- What bit version of ODP.NET (i.e. the Oracle Client Software) did you build your application on?
- What bit version of ODP.NET (i.e. the Oracle Client Software) do you want your application deployed on?
- What was the TargetCPU set to when you compiled your Application in Visual Studio?
You will achieve different levels of success when attempting to build and deploy your ODP.NET enabled application across 32-bit vs. 64-bit environments.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Trouble-Shooting Your Environment |
Solution |
CorFlags Conversion Tool (CorFlags.exe) |
ODP.NET Publisher Policy Files, .NET Framework 2.0 Support and Breaking Changes |
Application Configuration File (<AppName>.exe.config) |
Summary |
References |