![]() But ORACLE's 64-bit DLL won't run in this environment, so running and debugging on our local machines was something of an annoyance.īefore Visual Studio 2013 there was no easy way to run an app as a 64-bit process, so what we were doing was running locally using the 32-bit ORACLE DLL and then at deployment replacing that DLL with the 64-bit equivalent. When you start debugging a web site or application in VS, it spins up a 32-bit instance of IIS Express to host the process in. This is problem because Visual Studio is a 32-bit application. What I didn't realize until I started working with ORACLE about a year ago is that ORACLE actually cares about the architecture of the machine it is running on the x86 version of ORACLE's DLL will not run on an 圆4 machine and vice versa. Like most other shops (I believe), our servers run a 64-bit architecture. Now, however, we're running into a different set of problems. Our need to interface with ORACLE is what drove me and my team to develop a mapping system that allowed us to map ASP.NET DataTables to strongly-typed objects. The version of ORACLE we are using is very old (8+ years).We are almost exclusively a Microsoft shop. ![]() By itself this is not an issue (according to management), but problems arise from two things: Our organization, like many other medium-to-large companies, uses a central ORACLE database for most of our company-specific data.
0 Comments
Leave a Reply. |