Our (native) C++ app accesses an Oracle Database through OCI. (not OCCI)
We're currently compiling on VS2010. We want to migrate our code base to VS2015, and while it seems implied that OCI should work there, I noticed that the 12c Version of the OCI.dll statically links to MSVCR100.dll, which is the dynamic CRT lib of Visual Studio 2010.
Should I expect OCI 12c (Instant Client) access to work through a native C++ app compiled with the VS2015 toolset? (Or any Visual-C++ version newer that 2010, really.)
Our app would use the MSVCR* libs of 2015, and the OCI.dll would continue to ose the MSVCR100, which is not a problem in principle.
Disclaimer: Personally, I'd say: hell yes, sure it should work, but I can't find any official support statement (probably temporary search blindness), and I'm not really fluent with the full OCI API so I'm not sure whether there are corner cases where invalid stuff could be passed.
