May 27, 2015 10:08 PM|Lannie|LINK
Install the Oracle Data Access Components 12cR3 of later and select the CLIENT INSTALLATION option. (the classic Unmanaged driver version)
I would not install the Visual Studio Tools since you have two version of Visual Studio, I am uncertain of the outcome.
(you do not need the tools anyway, just the client and the driver).
If you are not operating in a FIPS-140 compliant environment, you can use the new MANAGED DRIVER which has the client build into the DLL and is bitness independent. You just need the TNSNAMES.ORA and the managed driver in your /BIN directory, and with some
additional setting in Web.config or app.config you are good to go for console, WinForm, WPF, and ASPX apps. The driver is relatively new and not full featured yet, but is fine for standard read and write to database functionality.
If you are operating in a FIPS-140 compliant environment, the MANAGED DRIVER will only work with the Oracle 12C database.
Otherwise you can use the traditional UNMANAGED ODAC driver, optionally installed in the /BIN folder of app with local reference or install in the GAC.
The READER is a function of the Oracle Data Access driver.
The 12C driver can connect to Oracle 12c, 11g, 10g, and (maybe earlier but I never tried that).
It can work with .NET 2.0 (use 2.0 driver version) or .NET 3.5 / 4.0 (using the 4.0 driver version).
You can download the 32-bit version or the 64-bit version, and compile to that environment.
Of course READING AND PLANNING to understand the requirements will reduce frustration of installation and implementation.