A client is 开发者_如何学Pythonrunning IIS with WOW64 enabled and is complaining that she cannot load our 64-bit DLL.
I have Delphi 2005 code that I use to retrieve database table field names. It works with no problems on 32-bit machines (Windows XP, Windows Vista, Windows 7).
Can someone please explain, simply, why it is necessary to go through so many hoops in order to run PowerShell (as an external command) from visual studio? I know it has to do with the bit differences
1) i am wanting to use a 32-bit dll that is not available as 64-bit dll 2) another constraint: Im wanting to also use another dll the 32bit version of which does not work in WOW64 so the second dll h
I\'m currently writing some test code in C++ that messes around with PE files to understand its file format structure. My project is set to compile to 64 bit. In my code I open %SystemRoot%\\system32\
I have a COM+ application开发者_开发问答 (mostly vb6 based), that I need running on a 64-bit system. It\'s supposed to communicate with an oracle database (10g, 32bit). Everything works fine when I di
I originally designed a win32 application on win7 32bits, with VC9.0. I recently upgraded to win7 64 bits, and tried to build+execute the previous application.
I need to compile a DLL in Managed C++ in Visual Studio 2005. I want it with 32Bit corflag on. See http://illuminatedcomputing.com/blog/?p=117 for reference.
I am using Wow64DisableWow64FsRedirection / Wow64RevertWow64FsRedirection to disable and restore WOW-64 file redirection (making system32\\ to syswow64\\ and some registry changes). The MSDN page warn
I\'m trying to buil开发者_运维技巧d a 32-bit program that can run correctly on 64-bit Windows; that is, if it needs to open a text file for the user, the file needs to not be redirected from C:\\Progr