AspNet error whith dll

Question

HI

Im migratin a WIN-FORM proyect to a new ASP.NET WEB-PROYECT. The problem is with a dll, this was made from a C++/CLI proyect, when I build the web site I get an error:

Could not load file or assembly 'F3BC4DNI_32' one of its dependencies. The located assembly's manifest definition does not match the assembly reference (Exception de HRESULT: 0x80131040)

Here the full error: Error here

Both proyects are using framework v4.

C++/CLI win32

People say that should use PInvoke, but I need to call the class name too and DllImport only works for methods (as I know).

Also People say I should add my dll to COM or .NET list. I run it with REGSVR32 but it gives me an error

Does anybody knows what could it be?

Thanks

Vulpes · Answer

Dependency Walker doesn't work properly with .NET dlls as there's no export table as such. However if it's a mixed mode C++/CLI dll it should be able to show you any exported unmanaged functions. It might or might not correctly show what other dlls are referenced. To check dependencies on a .NET dll I'd use a specialist tool such as ildasm.exe (available from VS Command Prompt) which should show you what external assemblies are referenced in the manifest.

Martin Eduardo Martinez Dimas · Answer

I used Dependecy Walker and the methods of a dll say are missing. But Why works when build a dll on Debug?

Vulpes · Answer

I assume you've copied your dll into the /bin folder of your website. If there are any custom (as opposed to system) dlls on which your dll depends I'd copy them to the /bin folder as well so the system can find them.

Martin Eduardo Martinez Dimas · Answer

Yes all projects are x86. I think I solved the problem changin the Debug option to Release in c++ project. but now a new error appears Could not load file or assembly 'MyDll.dll' or one of its dependencies. Can not find the specified module.

Vulpes · Answer

Are you sure that it's not just a versioning error i.e. you originally built the web site against an old version of the dll which you've now replaced with a newer version? If this is ringing any bells I'd check the version of the dll shown in web.config against the current version of the dll to see whether they differ.