This content has been marked as final. Show 7 replies
Visual Studio 2010 is a 32 bit application so you will also need to install the 32-bit ODAC beta to be able to use Entity Designer and the rest of the Oracle Developer Tools for Visual Studio.
64-bit ODAC is needed only if you intend to build 64-bit apps. Both 64-bit and 32-bit ODAC can coexist, but make sure to installl them in different Oracle Homes.
I will try that out :)
Yep. That worked for me. I actually uninstalled the 64-bit Oracle and client because I was having trouble installing the 32-bit client, even in a separate Home folder. So now I am running both 32-bit Oracle and a 32-bit client and VS 2010 easily finds my database.
Thank you very much!
I recently installed the ODAC 32-bit using the Oracle Universal Installer (OUI). I was able to connect to the server using code and Server Explorer. For the deployment on staging I am not allowed to use an installer so I uninstalled it and installed the XCopy version of ODAC 32-bit. Now I can connect to server using code but the server explorer is not showing ODP in the list of data providers.
I have also executed the following command-line utils:
c:\ora32>configure all ORA32 true
c:\ora32\odp.net\bin\4>OraProvCfg.exe /action:config /product:odp /frameworkversion:v4.0.30319 /providerpath:"C:\ora32\odp.net\bin\4\Oracle.DataAccess.dll"
and 2.x version of the same
But ODP did not show up. Any help...
where is the solution please:(
The solution is to use 32-bit ODAC with ODT installation, not the xcopy version. The xcopy version is intended for deployment time, not development time. Thus, the xcopy version does not contain any Oracle tools.
To further Alex's answer, the xcopy version contains the necessary files to use anything you build with the installer version. The only thing missing is the developer tools themselves, and you don't need those on your staging/production systems.