Change of version of Oracle.DataAccess?

Hello.

In a standard client 11 GR 2 installation, ODP.net comes with the 2.112.1.0 version. When you install the developer tools for VS, the installer replaces this version with 2.112.1.1.

When an application is built and then given to someone who doesn't have the developer tools, it has here a problem of version and the application fails to load the assembly (and therefore does not work).

So my question is this - why the developer tools contain a different version of Oracle.DataAccess.dll, and what is the best way to get around that?

Thank you.

Have you already checked the FAQ? You can target the previous versions of ODP using a newer ODT...
http://www.Oracle.com/technology/tech/dotnet/Col/odt_faq.html#olderodpnet

Greg

Tags: Database

Similar Questions

  • There are 2 versions of Oracle.DataAccess on the system with the same public token

    Hello
    can someone please explain this
    1 Oracle.DataAccess... x 86... 2.112.1.0... 89b483f429c47342
    2 Oracle.DataAccess... x 86... 2.112.2.0... 89b483f429c47342

    I have a reference in Visual Studio to one of these DLLs. My question:
    (1) what are the differences?
    2. what assembly is loaded by my application?

    greetings and thanks
    Ellen

    Hi Ellen,.

    All versions of the ODP assemblies have the same public key token. The difference is your case is you two versions (2.112.1.0 and 2.112.2.0) installed, and the difference between new features, bug fixes, etc.

    ODP also installs policy files by default that can come into play here, but it depends on which version you installed last. If you have installed 2.112.2.0 last, then the policy file would automatically redirect apps looking for 2.112.1.0 to use 2.112.2.0 instead.

    If you have installed 2.112.1.0 last, then the file 2.112 strategy would only redirect apps more 2.112.1.0 to use 2.112.1.0.

    If you're wondering how to determine what your application assembly IS actually responsible, the best way is via a tool like Process Explorer, which will allow that see you what libraries are loaded into a process.

    Greg

  • Oracle.DataAccess 32 bit and x 64 with a build? There is no corresponding version?

    We used Oracle.DataAccess to generate a .net assembly. version has been 10.1.0.400. I can't seem to find the x 64 native install for this 10.1.0.400 version we are running IIS in 64-bit mode. so I need an x 64 native bit Assembly.

    We deploy our .net assembly for a 32-bit and x 64 bit machines. so I need to install a version of Oracle.DataAccess with the same 32-bit and x 64 bit version.

    I can't find a version in common 32-bit and x 64 bit.

    It seems that the closer, I can get is 2.102.3.2 for x 64 and 2.102.2.20

    I have no problem re-construction of the Assembly, and as long as I can get the same fix on both 32 bit and x 64 bit version in the GAC, it should work very well. help, where can I find a corresponding 32-bit and x 64 bit version to install?

    Hello

    Yes, you must have a support account in order to login to metalink and get the fixes.

    Part of the ODP.NET installation includes installation of policy files in the GAC which redirect use the latest version installed, so I think you should be fine compilation on 10.2.0.2.21 x 86 (for example) and the distribution to the 10.2.0.3.02 x 64. You must compile a version<= the="" version="" you="" want="" to="" be="" able="" to="" run="" it="" on="">

    Greg

  • Intermediate language of the oracle.dataaccess.dll version

    Is there an intermediate version of the oracle.dataaccess.dll that we can use to compile 64-bit applications using 32-bit computers?

    We develop our applications on x 32 and deploy on x 64 (it is strictly enforced by our Organization. This means that there is no option for execution of x 32 code on an x 64 server).

    The oracle.dataaccess.dll only comes in 2 versions from what I can tell; x 32 or x 64. This forces us to use x 64 build servers. We need the x 32 ODP installed on our machines to dev for the development and the x 64 ODP installed on the servers of x 64 compilation. Dev of 32-bit machines cannot compile an application with an x 64 native dll.

    Example:
    1. create a new class library.
    2. Add the oracle.dataaccess reference.
    3. change the platform target in the properties of the project to x 64.
    4 compile the application.
    5 examine the dll in the bin directory. (I used the reflector, but you can use the corflags util)

    The target platform for the class library is x 64. The target platform for the oracle.dataaccess.dll is x 86. Application will not work when you run it as x 64.

    ODP.NET is the only 3rd-party product .NET we use which doesn't seem to have an intermediate language dll, and so the only reason why we allocate and maintain separate x 64 build servers to compile our code for x 64 deployment.

    It's been a while since I looked into that, so I was wondering if there is a solution now.

    I guess the poster is after a fully managed version of the provider, but maybe not.

  • Could not load file or assembly ' Oracle.DataAccess, Version = 4.112.4.0?

    Hi guys,.

    As the title says "could not load file or assembly ' Oracle.DataAccess, Version = 4.112.4.0. The program crashes when I try to run the following code.

    OracleConnection Con = new OracleConnection (ConfigurationManager.ConnectionStrings ["ConnectionString1"]. (ToString());

    SqlCmd OracleCommand = new OracleCommand();

    OracleDataReader dr;

    sqlCmd.Connection = Con;

    Con.Open ();

    sqlCmd.CommandText = "INSERT INTO ADFG values (0, 0, 0, ' ', sysdate);

    sqlCmd.ExecuteNonQuery ();

    sqlCmd.Clone ();

    MessageBox.Show ("inserted record!");

    Any help would be appreciated.

    Hello

    This occurs generally when there is an inconsistency in the application of ILO version and the version of ODP.NET bits.

    If you compiled/built the application with Any CPU option, please modify X 86 or X 64 and build and run the code.

    Thanks and greetings

    Vincent

    Support of Oracle

  • Could not load file or assembly ' Oracle.DataAccess, Version = 2.111.6.20

    I have visual Studio 2008 and ODAC installed Winows 7, my VS2008 application recovers data from Db Oracle 10 g xe. I get this error report wih spare no effort to connect and interact wih the database:

    "Could not load file or assembly ' Oracle.DataAccess, Version = 2.111.6.20,
    Culture = neutral, PublicKeyToken = 89b483f429c47342' or one of its dependencies.
    The system cannot find the specified file. »

    What could be the problem? The same code that worked on Vista is returning to this error report.

    Hello

    Oracle 11 g 2 32 and 64-bit client are available for download on:

    http://www.Oracle.com/technology/tech/dotnet/index.html

    That should solve the problem you have

    Thank you

    Mrinal

  • Oracle.Dataaccess.dll using unmanaged for 32 and 64 bit Winform application.

    Hello

    I am new to oracle ODP.

    I have a few questions about her.

    1. If I give the reference only and do not include gac Oracle.Dataaccess.dll (suppose 2.11.3.XX) in my project and the client system has the access.dll of oracle version 2.11.2.XX(or autres) then what happens?

    Be it use the 2.11.2.xx DLL to GAC or error.

    2. I need to create some app for 32 and 64-bit client then should I develop a version for two separate, or are there other alternatives (I can't use the managed oracle DLLS due to .net 2.0).

    I've already lost two days on managing versions of oracle as oci.dll ddll, oraop11s.dll etc.

    Please suggest any other alternative if you have

    Thank you

    I think that if you run an application on machine Win x 64 with AnyCPU, 64-bit .NET will be always charged. I don't think you can change this even if you try to load a 32-bit DLL. There may be a way, but I do not know myself.

    If you ODP.NET 11.2.0.3 on your system, I don't see why you need to install an earlier version of ODP.NET, such as 11.2.x

  • x 64 application entity Framework using Oracle.DataAccess.Client

    I am trying to build a x 64 application Entity Framework using the current Oracle.DataAccess.Client.  I can launch the application as Any CPU and x 86 using the managed provider, but when I compile for x 64, I get the error below when running. If I change the provider to Oracle.ManagedDataAccess.Client it works with x 86 and x 64 compiler.  Unfortunately, we are unable to use the managed provider until the xml is supported.  I have two clients x 86 and x 64 installed.  Any ideas?

    System.Data.EntityException was not handled

    HResult =-2146233087

    Message = the underlying provider failed to open.

    Source = System.Data.Entity

    StackTrace:

    at System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf (Boolean openCondition, storeConnectionToOpen of DbConnection, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean & closeStoreConnectionOnFailure)

    at System.Data.EntityClient.EntityConnection.Open)

    at System.Data.Objects.ObjectContext.EnsureConnection)

    to System.Data.Objects.ObjectContext.SaveChanges (SaveOptions options)

    at System.Data.Entity.Internal.InternalContext.SaveChanges)

    at System.Data.Entity.Internal.LazyInternalContext.SaveChanges)

    at System.Data.Entity.DbContext.SaveChanges)

    at EntityFramework1.EFTest.AddItem (c:\TFS2012\AD). NYSAS. ICPC\DEV\M01\EntityFramework1\EntityFramework1\EFTest.cs:line 21

    at EntityFrameworkConsole.Program.Main (String [] args) in c:\TFS2012\AD. NYSAS. ICPC\DEV\M01\EntityFramework1\EntityFrameworkConsole\Program.cs:line 12

    at System.AppDomain._nExecuteAssembly (RuntimeAssembly assembly, String [] args)

    at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly)

    at System.Threading.ExecutionContext.RunInternal (ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

    at System.Threading.ExecutionContext.Run (ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

    at System.Threading.ExecutionContext.Run (ExecutionContext executionContext, ContextCallback callback, Object state)

    at System.Threading.ThreadHelper.ThreadStart)

    InnerException: Oracle.DataAccess.Client.OracleException

    HResult =-2147467259

    Message =""

    ErrorCode =-2147467259

    StackTrace:

    at Oracle.DataAccess.Client.OracleException.HandleErrorHelper (Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx * pOpoSqlValCtx, ByVal src, String procedure, Bcheck Boolean, Int32 isRecoverable)

    at Oracle.DataAccess.Client.OracleException.HandleError (Int32 errCode, OracleConnection conn, IntPtr, Object src opsErrCtx)

    at Oracle.DataAccess.Client.OracleConnection.Open)

    at System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf (Boolean openCondition, storeConnectionToOpen of DbConnection, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean & closeStoreConnectionOnFailure)

    InnerException:

    Here is my web.config (less sensitive information):

    <? XML version = "1.0" encoding = "utf-8"? >

    < configuration >

    < configSections >

    < section name = "EF" type = "System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, Entity Framework, Version = 5.0.0.0, Culture = neutral, PublicKeyToken = b77a5c561934e089' requirePermission ="false"/ >"

    < / configSections >

    < Entity Framework >

    < defaultConnectionFactory type = "System.Data.Entity.Infrastructure.LocalDbConnectionFactory, Entity Framework" >

    < Parameters >

    < setting = "v11.0" / >

    < / Parameter >

    < / defaultConnectionFactory >

    < / Entity Framework >

    < connectionStrings >

    < add name = 'Entities' connection string connectionString="metadata=res://*/Models.EFEntities.csdl|res://*/Models.EFEntities.ssdl|res://*/Models.EFEntities.msl;provider=Oracle.DataAccess.Client;provider = & quot; data source = DATASOURCE; password = PASSWORD; persist info security = True; user ID = username & quot; "" ProviderName "/ >

    < / connectionStrings >

    < / configuration >

    Alex,

    Finally, we have solved the problem.  It turns out that we had a bad x 64 home path in the PATH variable.  I lost track of what it was originally, but I'm sure the x 64 bin path was correct. I did not notice that it was wrong, until I tried to install the full client and began to see an error indicating that it was missing a dll.  This led me to a post on the forum, in which you indicated that the PATH variable has not been set (ODAC 12 c for xcopy issues).  In our case, it is not missing, just fake.

    This is the behavior that we see if the PATH variable for the home directories and bin is incorrect:

    • Full client: an error of external system (no exceptions).  The error message is that the oraons.dll is missing.
    • XCOPY customer: generates an exception without error message.  The Exception.Message property is empty and there is no inner exception.

    Can the ODP team can add a meaningful message for this exception?  If the exact error cannot be highlighted during execution, a generic name on the path audit would help enormously.  I must have looked at it a dozen times and didn't notice that it was false.  If I had no idea that this could be the cause, it would be discussed more in detail, or had someone else Verify that it was correct.  I hope that we would have solved much earlier.

    Thank you.

  • Could not load file or assembly ' Oracle.DataAccess error on server

    I construisent.net application on my Machine local Windows 7 and I have the 32-bit Microsoft installed on my machine that works well with VS 2010.

    I placed it on the server and when I open the page that accesses data from Oracle, I get the error below. The server and my local computer have the Oracle.DataAccess
    DLL installed and both have the same public token 89b483f429c47342. I changed the CPU of Any CPU target to x 86 and published a Release version of my project to the server.

    Why I get the below error?

    ==========================================================================================================
    Could not load file or assembly 'Oracle.DataAccess, Version = 4.112.2.0, Culture = neutral, PublicKeyToken = 89b483f429c47342' or one of its dependencies. The system cannot find the specified file.
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and its origin in the code.

    Exception details: System.IO.FileNotFoundException: could not load file or Assembly 'Oracle.DataAccess, Version = 4.112.2.0, Culture = neutral, PublicKeyToken = 89b483f429c47342' or one of its dependencies. The system cannot find the specified file.

    Source error:

    An unhandled exception is generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception below stack trace.

    Assembly Load Trace: the following information may be helpful to determine why the assembly 'Oracle.DataAccess, Version = 4.112.2.0, Culture = neutral, PublicKeyToken = 89b483f429c47342' could not be loaded.


    WRN: Assembly binding logging is disabled.
    To enable the failure of link Assembly record, set the registry value [HKLM\Software\Microsoft\Fusion! EnableLog] (DWORD) to 1.
    Note: There is some pain associated with a record of failure performance link Assembly.
    To disable this feature, remove the registry value [HKLM\Software\Microsoft\Fusion! EnableLog].



    Stack trace:


    [FileNotFoundException: could not load file or assembly 'Oracle.DataAccess, Version = 4.112.2.0, Culture = neutral, PublicKeyToken = 89b483f429c47342' or one of its dependencies.] The system does not find the specified file].
    antac.dashboard.Page_Load (Object sender, EventArgs e) in C:\Users\George\Documents\Visual Studio 2010\Projects\antac\antac\dashboard.aspx.cs:92
    System.Web.Util.CalliHelper.EventArgFunctionCaller (fp IntPtr, Object o, object t, e As EventArgs) + 25
    System.Web.UI.Control.LoadRecursive () + 71
    System.Web.UI.Page.ProcessRequestMain (Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) + 3048




    --------------------------------------------------------------------------------
    Version information: Microsoft .NET Framework Version: 4.0.30319; ASP.NET Version: 4.0.30319.1

    This isn't the only DLL that is required. You must fully install ODP.NET on the server.

  • Only 32-bit Oracle.DataAccess.dll

    Hello

    I have the Oracle Client 11.2.0 32bits and 64bits installed side-by-side. When I run CORFLAGS. EXE on the Oracle.DataAccess.dll located in the 32 bit folder Bin of ODP NET and then run it on the dll, which is located in the Bin folder of 64 bit, here are the results:

    Oracle.DataAccess.dll (from folder for 32-bit)

    CorFlags Microsoft(r) .NET Framework Conversion tool.  Version 4.0.30319.1
    Copyright (c) Microsoft Corporation.  All rights reserved.

    Version: v4.0.30319
    CLR header: 2.5
    PE: PE32
    CorFlags: 24
    ILONLY: 0
    32 BITS: 0
    Signed: 1


    Oracle.DataAccess.dll (from 64-bit folder)

    CorFlags Microsoft(r) .NET Framework Conversion tool.  Version 4.0.30319.1
    Copyright (c) Microsoft Corporation.  All rights reserved.

    Version: v4.0.30319
    CLR header: 2.5
    PE: PE32
    CorFlags: 24
    ILONLY: 0
    32 BITS: 0
    Signed: 1

    Are these 2 files 'AnyCPU' which, in .NET, would make the binary 32 bits? Is there a 64-bit version of this DLL?

    Thanks in advance,

    Richard

    Sorry, I correct myself... DLLs are correct. I have a batch file that executes corflags on about 15 dll from a project that gives me an BadFormatImage exception, and I had made a mistake in the batch file. That made me believe that there is something wrong with my OClient. The corflags results now display correctly:

    32-bit Oracle.DataAccess.dll

    CLR header: 2.5
    PE: PE32
    CorFlags: 11
    ILONLY: 1
    32 BIT: 1
    Signed: 1

    Oracle.DataAccess.dll 64-bit

    CLR header: 2.5
    PE: PE32 +.
    CorFlags: 9
    ILONLY: 1
    32 BITS: 0
    Signed: 1

    Thank you Alex

  • Failure of Oracle.DataAccess.Client on the Prod Server

    Our site Asp.net/Vb.net (.net 4) fails to load when left dev for the production. Works without problems on Dev

    (Dev is Windows 7 32-bit)

    (Production is Server 2008 64-bit)

    Application pool is .NET v4.0, 32-Bit = True, the PipeLine Mode = Integrated

    The site connects to an Oracle 11 g via ODAC 12 c Release 2 (12.1.0.1.2) base the same version has been installed on the Production as well.

    We use TNSNAMES, it has been tested on Production and works.

    What I am doing wrong?

    Below is the error I get.

    Server Error in '/' Application.
    --------------------------------------------------------------------------------

    Unhandled Execution Error
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: Oracle.DataAccess.Client.OracleException:

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

    Stack Trace:


    [OracleException (0x80004005)]
      
    Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure, Boolean bCheck, Int32 isRecoverable) +1601
      
    Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, Object src) +61
      
    Oracle.DataAccess.Client.OracleConnection.Open() +5329
      cpsweb
    .com.clsDB.Get_DataTable(String sSQL) in D:\SourceVaultLocal\WebSites\cpsweb.com\CPS_Code\clsDB.vb:42
      cpsweb
    .com.clsSec_Security.isVisible(String sPageName, Object& oObj) in D:\SourceVaultLocal\WebSites\cpsweb.com\CPS_Apps\Sec_WebSite\Code\clsSec_Security.vb:50
      cpsweb
    .com._Default.Page_Load(Object sender, EventArgs e) in D:\SourceVaultLocal\WebSites\cpsweb.com\Default.aspx.vb:20
      
    System.Web.UI.Control.OnLoad(EventArgs e) +91
      
    System.Web.UI.Control.LoadRecursive() +74
      
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207

    --------------------------------------------------------------------------------

    If it turns out that.  The drivers do not install correctly.

    I added the following key

    HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\

    key = 'NLS_LANG.

    value = "AMERICAN_AMERICA. UTF8.

    do you have an iisreset, and of course the site came right up.

  • System.Data.OracleClient migration to 4 Oracle.DataAccess issues

    I'm trying to convert a great demand out of the obsolete microsoft api to oracle dataaccess.

    But I faced a no-go - possible.

    I have this request:

    UPDATE TSUTCMP0

    SET

    DT_INI_CMP =: DataInicio / * I just omitted other parameters to simplify * /.

    WHERE

    CD_SEQ_CMP =: Código

    Then to run this query and many others I like the following:

    using (var = new TransactionScope() scope)

    using (var conn = MethodToCreateConnection()) / / this method simply creates: DbProviderFactories ("Oracle.DataAccess.Client"). CreateConnection()

    using (var cmd = conn. CreateCommand())

    {

    cmd.CommandText = requesting one;

    var p is cmd. CreateParameter();

    p.ParameterName = "DataInicio";

    p.Value = someDate;

    cmd. Parameters.Add (p);

    cmd ExecuteNonQuery());

    }

    This used to work using microsoft api. I have hundreds of querys, using parameters.

    When I run the present by using the Oracle.DataAccess, I get the following:

    {ORA-00932: inconsistent data types: expected DATE obtained NUMBER}

    In this case, the column in the table is DATES. I inspected the OracleParameter p and DbType is of type DateTime and OracleDbType is TimeStamp. Tried to force OracleDbType far without success.

    I also queries with columns of type DATE that stores the date and time.

    I don't know what I'm missing.

    MS OracleClient binds parameters by name. ODP.NET links in position. If you want to change the ODP. NET default binding behavior, set:

    OracleCommand.BindByName = true;


    Do this for each OracleCommand object that binds the parameters.

  • Release of the ODAC 4 &amp; 5 - Oracle.DataAccess.dll 4.112.3.0

    Has anyone else noticed that ODAC version 4 and 5 have the same 4.112.3.0 AssemblyVersion?

    Oracle (ODAC) for Windows data access components

    It took me a while to spot the problem.  I use Entity Framework 5 and hitting a machine with version 4.  He threw a completely misleading exception on the laundry.

    System.Reflection.TargetInvocationException: Exception was thrown by the target of a call. -> System.TypeInitializationException: the initializer for type for 'Oracle.DataAccess.Client.OracleConnectionStringBuilder' threw an exception. -> System.TypeInitializationException: the initializer for type for 'Oracle.DataAccess.Client.RegAndConfigRdr' threw an exception. ---> System.Configuration.ConfigurationErrorsException: MySchema.MyPackage.MyProcedure.RefCursorMetaData.CUROUT.Column.1 is not valid

    at Oracle.DataAccess.Client.RegAndConfigRdr.AddMetadataForRefCursor (String refCursorKey, String metadataInfo, Hashtable & schemaTable)

    to Oracle.DataAccess.Client.RegAndConfigRdr.RetrieveInfoFromConfig (NameValueCollection nvc, Hashtable & schemaTable, Boolean bIsCallFromODT)

    to Oracle.DataAccess.Client.RegAndConfigRdr... cctor()

    Since version 4 ODAC has been installed, the machine had Oracle.DataAccess.dll (4.112.3.0) in the GAC.  So, my application could not use my local copy of Oracle.DataAccess.dll (4.112.3.0) of version 5.

    There are problems with having the AssemblyVersion similarly for version 4 and 5.  Can we get an extra release with an updated version?

    There are two questions in your last post:

    (1) Oracle.DataAccess.dll versioning

    (2) DLL's Client Oracle unmanaged referenced by Oracle.DataAccess.dll

    The forum post you quote refers to the #2 problem.

    Problem #1, preferred the ODP.NET team is at version every single Oracle.DataAccess.dll version. We can not due to a conflict with the policy of general correction of Oracle. With the help of AssemblyInformationalVersionAttribute is the best compromise.

    If you have already downloaded an Oracle patch, you will notice the files share the same version number as other patches within a family group of patches Oracle. With each new group of patches or major version, Oracle.DataAccess, dll can then increase its version, just like every other DLL of Oracle.

  • Could not load file or assembly Oracle.DataAccess

    I have a VB.Net application that worked fine on a Windows 2003 32-bit secure server for many months. Exe has already been compiled on a 32-bit Vista machine and then the exe has been copied to the server. Today, I was delivered a new 64-bit Windows 7 computer. I installed the 32 bit ODAC 11.2.0 and added a reference to Oracle.DataAccess.dll in Visual Studio 2010. The program compiles and runs normally on my 64 bit Windows 7 computer. In Visual Studio 2010, I 'CPU target' defined on x 86.

    When I copy the exe on the 32-bit server, the following error message is returned: "could not load file or assembly Oracle.DataAccess.

    The server has two facilities of ODAC 32bits, 11.2.0.2 and 10.2.0. Why does this work?

    Published by: Francis November 1, 2012 13:02

    It's been awhile that I'm on version issues, so I'm a little fuzzy, but I think the problem here is that you develop against a newer version (even if only a little) of the Assembly, that which exists on the deployment target computer. There are policy files to redirect the old versions of the assembly to the latest version installed on the computer, but it does not work to redirect a newer version (i.e. 2.112.2.0) downwards (i.e. 2.112.1.0).

  • How to refer to 64-bit Oracle.DataAccess.dll in VS2010?

    Hello!

    We installed the ODAC 64-bit 4.112.2.0 on our new developer computers. With the 32-bit version of the ODAC, we would do this option to add the oracle references: Add reference-> tab .NET and add Oracle.Web.dll and Oracle.DataAccess.dll. But after our transition to 64-bit files exist no more. We could do something like make a local reference (include the bin folder in project and place the files and point of reference to them for an example) but this does not seem like a good solution. Has anyone else experienced this problem and solved?

    /regards

    You need not reference on x 64 version. You can add the reference on x 86 version. If you want to run the VS project, you need x 86 version customer Oracle VS x 86 application.

    The two DLLS ODAC (x 86 and x 64) has the same signature. If you build the project with the option "any cpu" then right what ODP.NET version is used for execution.

Maybe you are looking for