This content has been marked as final. Show 6 replies
If it's possible to use it instead, take a look at the new managed client beta. That's a single .net assembly you include in the project, no Oracle installation required. It makes this type of scenario vastly easier (in fact we fixed this problem in a project just two days ago by using it).
My understanding (and experience so far) is that I still need some other Oracle DLLs. My problem is that I need the 64 bit bits available at runtime and the 32 bit bits available during install.
Also, it seems like I need to have a config file or .ora files, which is problematic during install. Is it not possible to specify the connection settings in code only?
Is it really possible to include just the managed client asssembly, nothing else, and have things work? It's possible my previous issues were due to Oracle connectivity being missing during the install, but I've tried so many permutations that I don't remember exactly what went wrong yesterday.
Edited by: colin_young on Nov 28, 2012 5:33 PM
That's what the managed client is specifically for, yes. One assembly included in the project (using Copy Local = true), and you've got Oracle connectvity. No installations and no extra DLLs. You can put the connection info into your config file with the application, so no .ora files are needed either.1 person found this helpful
It's by far the simplest way to solve this problem.
But, is the .config file required? I need to make the Oracle call during install, so there is no config file (and I can't figure out if it it possible to have one for a custom actions project).
Don't know, I've never tried it without one.
I also don't know if it's going to work during install, unless your installer is a .net application itself. You could refactor whatever you're doing during install to do in a post-install application startup instead, which would get around that.
Thanks. It would be nice to get some official feedback or guidance on installing. The existing documentation (on all Oracle client distributions, not just this beta managed driver) could charitably be called confusing.
I tested the install using the EZ Connect syntax and it doesn't work (the custom action in the installer is .Net code and has a reference to the managed provider).