the module was expected to contain an assembly manifest

Rate this:

Please Sign up or sign in to vote.

See more:

I'm having a lot of issues not only with Visual Basic 2008 but with other programs as well on my Windows XP SP2 operating system. I googled this subject but couldn';t find what I was looking for.

This is what happened. When I tried to test an application on Visual Basic 2008, it comes up with this infamous error:

Error while trying to run project: Could not file or assembly "WindowsApplication1" or any of its dependencies. The module was expected to contain an assembly manifest.

I know it's not a Visual Studio problem and it's not a project problem. This happens to ALL projects even when I start a new project. And tried renaming my project as well. I recently re-installed my Operating system fresh. I firstly loaded all the Dot Net Frameworks 1, 1.1, 2, 3 and 3.5 then Visual Studio. Within the first thirty minutes I tested an application and it works fine - any project works fine! I left it for an hour while doing other stuff on the computer and tried to test the application again. And the error came up! I got so annoyed and it's just a fresh PC!

This is odd - I try to install a software that requires Dot Net 3.5 and asks me to install it when I already have it installed! It won't install it again because it's already installed, and it requires an internet connection which I don't have on my windows xp operating system (not the one i'm using now).

And I don't know where the log files are. I'm supposed to have FusionLog or something but it's not included here.

Can anybody help please?

Posted 2-Dec-12 22:38pm

Gruntkiller4000323

Updated 2-Dec-12 22:39pm

Add a Solution

Rate this:

Please Sign up or sign in to vote.

Solution 1

right click the project and select Clean and then build it again. Or manually delete all the temprary files and folders under project and the rebuild it. This enables the project was build and the files are existed.
close Visual Studio first and then reopen in through command prompt with /safemode option. This enables VS avoid third part add-ins.
restart the computer and enter into safe mode.

or

right click the project and select Clean and then build it again. (still the same, error message pop out)
close Visual Studio first and then reopen in through command prompt with /safemode option. This enables VS avoid third part add-ins.(how to open in through command
prompt?) restart the computer and enter into safe mode.

Permalink

Posted 2-Dec-12 22:42pm

KrunalRohit61.7K

Comments

Gruntkiller4000 3-Dec-12 5:50am

Okay. Thanks for the quick reply. I have noticed clean does not exist in the BUILD menu. I also forgot to mention the build DID succeed. But the error message comes up anyway. Tried in safe mode for visual basic, same error. I rebooted into safe mode and tested the project - the error happens again. Then the "Clean" appears in the Build menu. Strange. I cleaned the project and re-tested and still didn't work. So I think the error either has something to do with Dot Net Framework and/or the system itself.

the module was expected to contain an assembly manifest

1 solution

Solution 1

Add your solution here

Preview 0

the module was expected to contain an assembly manifest

1 solution

Solution 1

Add your solution here

Preview 0

Existing Members

...or Join us