The module was expected to contain an assembly manifest. (Exception from HRESULT: 0x80131018)

Question

3.50/5 (2 votes)

See more:

Dear Sirs...

I created a system that loads a plugin (DLL) at runtime. Everything works perfectly fine. I installed this system on 15 machines , and added the plug in and no error happened for 13 machines and everything worked as expected.

Two machines rejected the plugin with this error.

C++

The module was expected to contain an assembly manifest. (Exception from HRESULT: 0x80131018)

as I said before everything works perfectly fine on 13 machines. Only two machines are triggering this kind of error.

any idea regarding this error?

thank you.

[Edit further information from OP]
One of the machines is Win7, the other is win xp, and I am using .net 3.5. The other 13 machines which are running the exe without problem, has win7, xp, and vista.

[/Edit]

Posted 10-Mar-11 4:20am

Member 7742860

Updated 10-Mar-11 4:58am

Henry Minute

v2

Add a Solution

Comments

thatraja 10-Mar-11 10:41am

which language? .NET? vb? please complete the question & clearly

Member 7742860 10-Mar-11 10:44am

Yes I am using VB.NET to develop the application. But the error is triggered by the installed exe.

thank you.

Henry Minute 10-Mar-11 10:43am

Also which OS on each machine which version of the .NET Framework.

Member 7742860 10-Mar-11 10:46am

One of the machines is Win7, the other is win xp, and I am using .net 3.5. The other 13 machines which are running the exe without problem, has win7, xp, and vista.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2011-03-10T04:44:00

Solution 1

A quick Google suggest that this occurs when there is a native code DLL of the same name as a managed DLL.
Try changing the name of yours and see if it goes away.

http://www.google.co.uk/search?sourceid=chrome&ie=UTF-8&q=The+module+was+expected+to+contain+an+assembly+manifest.+(Exception+from+HRESULT:+0x80131018)[^]

Posted 10-Mar-11 4:44am

OriginalGriff

Comments

Henry Minute 10-Mar-11 10:48am

Good find!

Member 7742860 10-Mar-11 10:52am

Dear Sir,

thanks for the answer, I already googled and found such answer. I have no native and managed DLL working togather, also, the same exact application works fine on 13 machines.

so this still don't answer my question.

thank you

OriginalGriff 10-Mar-11 10:53am

No, but do the two machines it doesn't work on know that?
If they have a unmanaged DLL of the same name installed by another program...

Member 7742860 10-Mar-11 10:57am

They don't have another DLL with the same name simply because I am the one who created the DLL, so I am totally sure that this is not what is causing the issue.

thank you.

OriginalGriff 10-Mar-11 11:04am

Yes, but did you install all the software on those machines? Could another application have installed a DLL of the same name?
It would explain the difference between the 2 and the 13

Member 7742860 10-Mar-11 11:11am

No other software could have installed the DLL. This is what the code does:
1- user selects the DLL or plug in file
2- application copy the file into a special temp directory under the exe's directory structure. the plugin name is changed to be a specific file name, such that there is no other dll file with the same name.
3- reflection is used to load the DLL
4- a test for the DLL is being made.
5- if the DLL is okay, it is placed in a plugin folder with a distinct name to be loaded next time the app starts up.

I am getting the error in step 3.

thank you.