Visual Studio: Error loading DLL

Question

I've got a C# dll and wanted to import it in stdafx.h (another DLL for JNI): import "C:\Users\Marcus Tik\Documents\Visual Studio 2010\Projects\DotNETSpy\DotNETSpy\bin\Release\DotNETSpy.dll" -> Visual Studio said: "Error loading DLL."

Then I used Dependency Walker which says Error: "Modules with different CPU Types where found."

Isn't it standard for a C# DLL to support different CPU Types? How can I solve my problems ? Thanx in advance!

Depends is quite unsuitable for managed assemblies. You can't get a better answer until you describe what you actually want to accomplish. — Hans Passant, Mar 09 '12 at 13:34
Are you using #import - i.e. are you trying to import a COM object defined in C#? — Phil, Mar 22 '12 at 17:37

sloth · Answer 1 · 2012-03-09T13:23:11.343

4

If you want to check dependencies on a .Net assembly, better use CheckAsm instead of Dependency Walker (at least if you want to see the managed code dependencies, which you probably want).

You can compile managed .Net libraries to 'AnyCPU', so you usually don't have to worry about 32-/64-bit issues. But maybe your DLL depends on an unmanaged DLL, which may cause trouble if the unmanaged library is e.g. 32-bit and you're trying to run it on a 64-bit machine.

edited Mar 09 '12 at 13:23

answered Mar 09 '12 at 13:17

sloth

99,095
21
171
219

I tried to download CheckASM but IE says: "CheckASM is not downloaded often and can do harm to your PC." – Marcus Tik Mar 09 '12 at 13:21
1

Really? Just download it anyway. It won't warm your PC. It's just a generic warning message. – sloth Mar 09 '12 at 13:25
Just downloaded CheckASM with Firefox -> everything OK CheckASM reports no errors on my C# DLL. – Marcus Tik Mar 09 '12 at 14:14
Try building for x86 explicitly, that might solve some issues ! – squelos Mar 09 '12 at 14:31
I selected Win32 on my Visual Studio 2010 Express but I still get the error. – Marcus Tik Mar 09 '12 at 15:27
Change the Build option to x86, you might be trying to import a 32 bit OS dll into 64 bit environment – Varun Goel Mar 23 '12 at 03:45

score 1 · Answer 2 · edited May 23 '17 at 12:22

1

Change the Build option to x86, you might be trying to import a 32 bit OS dll into 64 bit environment.

Check out this link: Access x86 COM from x64 .NET

edited May 23 '17 at 12:22

Community

1
1

answered Mar 23 '12 at 03:47

Varun Goel

339
3
15

score 0 · Answer 3 · answered Mar 17 '12 at 06:49

0

If your OS is 32bit and the dll is compiled exclusively for 64bit I think you get that result.

answered Mar 17 '12 at 06:49

Mattias Åslund

3,877
2
18
17

score 0 · Answer 4 · answered Mar 23 '12 at 13:35

Trying to make the Debug version work is pretty pointless, you can't get the debug version of the CRT libraries deployed. Beware that Dependency Walker is running out of gas on modern executables, it knows nothing about manifests. It will always show them as missing, even when they are not.

The two solutions for this case would be to either use it as a private assembly or to statically link. But remember, this is only for debugging and you should not distribute these files since it is agains the Microsoft terms.

Visual Studio: Error loading DLL

4 Answers4