You can only load a 32bit DLL into a 64 bit process when you are loading the dll as a datafile. You can’t execute the code. (http://support.microsoft.com/kb/282423) Microsoft recommends that you use interprocess COM to use 32 bit code with a 64 bit application. Here’s an article explaining the process.
Windows dll error 126 can have many root causes. The most useful methods I have found to debug this are: Use dependency walker to look for any obvious problems (which you have already done) Use the sysinternals utility Process Monitor https://learn.microsoft.com/en-us/sysinternals/downloads/procmon from Microsoft to trace all file access while your dll is trying to load. … Read more
This is what I do: Create a lib folder at the solution level Download and copy all my third-party DLL files into there Reference from the lib folder Put all those DLL files in the source control. I am using Subversion, and I add them manually but this is one-off. You can also add a … Read more
comdlg32.dll is not a COM DLL and cannot be registered. One way to confirm this for yourself is to run this command: dumpbin /exports comdlg32.dll You’ll see that comdlg32.dll doesn’t contain a DllRegisterServer method. Hence RegSvr32.exe won’t work. That’s your answer. ComDlg32.dll is a a system component. (exists in both c:\windows\system32 and c:\windows\syswow64) Trying to … Read more
Assembly loading is a rather elaborate process which depends on lots of different factors like configuration files, publisher policies, appdomain settings, CLR hosts, partial or full assembly names, etc. The simple version is that the GAC is first, then the private paths. %PATH% is never used. It is best to use Assembly Binding Log Viewer … Read more
On Visual Studio 2011, this worked for me: Project -> “project” Properties -> Configuration Properties -> General -> Project Defaults -> Use of MFC : Use MFC in a shared DLL (In Visual Studio 2019, the latter setting can be found in “Properties -> Configuration Properties -> Advanced -> Use of MFC“
Specifying the path to the DLL file in your project’s settings does not ensure that your application will find the DLL at run-time. You only told Visual Studio how to find the files it needs. That has nothing to do with how the program finds what it needs, once built. Placing the DLL file into … Read more
From this page (untested by me): Somewhere in your program’s initialization (before you access any classes from a referenced assembly) do this: AppDomain.CurrentDomain.AppendPrivatePath(@”bin\DLLs”); Edit: This article says AppendPrivatePath is considered obsolete, but also gives a workaround. Edit 2: Looks like the easiest and most kosher way to do this is in the app.config file (see … Read more
I have a .NET 4.0 dll project that is being called by a .NET 2.0 project. Is there a way to reconcile the difference in framework? Not that way round, no. The .NET 4 CLR can load .NET 2 assemblies (usually – there are a few exceptions for mixed-mode assemblies, IIRC), but not vice versa. … Read more
You need to install the Visual C++ libraries: http://www.microsoft.com/en-us/download/details.aspx?id=30679 As mentioned by Stuart McLaughlin, make sure you get the x86 version even if you use a 64-bits OS because PHP needs some 32-bit libraries.