eidercom wrote:That's a bad idea. As soon as you move that project to another system with a different version of Oracle client, it's going to blow up. That'll even happen if that version of Oracle is one your project could otherwise work with. (God help you if you write something portable using AnyCPU.)
2. In my WPF and ASP.NET applications, I routinely put the appropriate version of Oracle.DataAccess.dll in the project /BIN folder and make a local reference to it. And using code behind form, make ODP.NET calls with no problems.
3. I have not gotten the Visual Studio stuff working in ODP.NET over many versions of Oracle, VS Studio, and ODP.NET over the years, and heck..who really needs it. Write your own code and queries.If you use the ODTWithODAC package it installs just fine. I'm using it right now. The tools are pretty handy since they contain the Entity Framework support, and why write boilerplate queries when Oracle can do it for me?
984859 wrote:Yeah, that does effect things. Your main problem is Windows 8 right now, since there's no release for it. That said:
PS: I did notice that VS 2012 is a 32 bit app. Do not know if it informs your answer. Thanks a lot!