Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got some .Net software that's using a DLL of Oracle is ODP.Net that is tagged as version What database release does that map to? Is there any pattern to how they name these things?

share|improve this question
up vote 2 down vote accepted

From the ODP FAQ:

Q: In ODP.NET and higher, why does the same ODP.NET provider have two different version numbers?

A: For ODP.NET and higher, the same ODP.NET binaries have two different version numbers when viewed from either .NET products (e.g. Visual Studio 2005 would see version or when viewed from Oracle products (e.g. Oracle Universall Installer would see version Prior to ODP.NET, the latter versioning was employed exclusively. The use [of] the second versioning method was necessary to properly support .NET policy files for .NET Framework 1.x and 2.0.

Here is the version scheme:

For example, if the ODP.NET product version number is, the corresponding ODP.NET assembly versions are:

  • .NET Framework 1.x version:
  • .NET Framework 2.0 version:

Your version therefore refers to Oracle, for the .NET 2.0 framework.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.