My problem and the solution I have a 32 bit third party dll which I have installed in 2008 R2 machine which is 64 bit. I have a wcf service created in .net 4.5 framework which calls the 32 bit third party dll for process. Now I have build property set to target ‘any’ cpu … Read more
load-time linking is when symbols in the library, referenced by the executable (or another library) are handled when the executable/library is loaded into memory, by the operating system. Run-time linking is when you use an API provided by the OS or through a library to load a DLL or DSO when you need it, and … Read more
As others indicated, stdole.dll is a Primary Interop Assembly for a bunch of Office COM interop components. You can determine why it’s getting included in your project by doing the following. In Visual Studio, go to Tools > Options > Projects and Solutions > Build and Run. Change the “MSBuild project build output verbosity” setting … Read more
I ran into this issue as well. However my fix was much easier. My file names and paths were too long to be zipped. There was no warning. I resolved it by copy-pasting the directory to another with a shorter path. e.g. from /this/path/is/way/too/ooo/ooo/oo/long to /home/Desktop
The problem is likely you try to register a 32-bit library with 64-bit version of regsvr32. See this KB article – you need to run regsvr32 from windows\SysWOW64 for 32-bit libraries.
Have a look at BoxedApp. Good luck!
The answer depends on what language the DLL was written in. If it was a .NET language then, as pointed out, you can use .NET Reflector. If it’s the older Visual Basic (pre-.NET), then the DLL is compiled as what’s called p-code and there are a few options for doing some variations on decompiling. Finally, … Read more
I’m currently on Windows 10 build 1809, and depends.exe hangs for every dll I try it with. The depends home page says “Dependency Walker runs on Windows 95, 98, Me, NT, 2000, XP, 2003, Vista, 7, and 8” so I guess it’s not supported. Try Dependencies – An open-source modern Dependency Walker, it works fine … Read more
Naming the output file libjvm.dll.a will allow gcc to recognize it as a library named jvm. The .dll.a suffix indicates (by convention) that it is an import library, rather than a static library (which would simply be named libjvm.a, again by convention).
It turns out to get this application working under VBScript, I had to do two things. Run RegAsm.exe to register the DLLs. Run the C:\Windows\SysWOW64\cscript.exe to run my VBScript. If these don’t work, check out the other answer here about enabling 32-bit applications in IIS.