Everything seems to be working good and the computer is running noticeable faster with a lower resource usage.
The only drivers that I needed were for the video controller and the finger reader. Windows 7 did a pretty good job of finding and configuring my hardware. I was installing on a Dell Latitude D630 with a nVidia video controller. The base installation was quick and painless. Just to make things interesting, I also moved to the 64 bit version.
I started the move to Windows 7 last night. Hope this helps … Posted on Octoby rinsalaco Posted in How-To Leave a comment Windows 7 Installation … This setting can be found at Project > Properties > Compile > Advanced Compile Options. At lest for the application that I am working on now, I was able to tell Visual Studio that the target CPU was a x86 and then everything ran fine. It is the act of the COM object running in the WOW64 subsystem making a call to a 32-bit object that is causing the problem. (Exception from HRESULT: 0x8007007E)”Īfter digging around, I found this is because I am calling a COM object that in turn is calling a 32-bit object which is not supported. “System.DllNotFoundException: Unable to load DLL ‘SERVICES’: The specified module could not be found. If I compile the project and run it on a 64-bit system, to program runs fine until I make a call against the API.
In my Visual Studio 2008 project I have a reference to a dll file that exposes the API needed to access the business rules and import or export data. There is still some legacy code that they need to get migrated, and they are working on a full 64-bit update. The ERP system that I am connecting to is a 32-bit application and it will NOT run on a 64-bit system. I am working on a data collection system that will integrate with our ERP system and is accessing it through the API that they provide. This was a new problem for me since I rarely ever need to write software that calls a COM object that is running on a second machine.
0 kommentar(er)
