Error while trying to run project: Could not load file or assembly 'WindowsFormsApplication1' or one of its dependencies. The module was expected to contain an assembly manifest.

Question

0.00/5 (No votes)

See more:

I am facing a new problem with my project

Yesterday it worked good.. I shutdown my system and came back to my work with the project today,

it is showing the error

Error while trying to run project: Could not load file or assembly 'Amber' or one of its dependencies. The module was expected to contain an assembly manifest.

I searched in google and done the following to solve this problem......
1. I set my project as startup project
but no use
2. Deleted the Temp folder
then also getting same error
3. I Removed all the references and added freshly
but same error exists

Now...I created a new project "WindowsFormsApplication1" and placed a default empty form
Even if I run this simple form project, I am getting same problem

Error while trying to run project: Could not load file or assembly 'WindowsFormsApplication1' or one of its dependencies. The module was expected to contain an assembly manifest.

plz help me to solve this problem
I am not understanding the problem,,, wheather it is in my project or visual studio
my entire one month work is seems to be gone,,,,,,,,,,,,,,,plz help me,,,,,,

Posted 24-Jan-12 23:16pm

muzaffar527

Updated 24-Jan-12 23:30pm

ambarishtv

v3

Add a Solution

Comments

Addy Tas 26-Jan-12 17:00pm

Have you tried Dependency checker from the sysinternals suite?

2 solutions

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)

jschell · Answer 1 · 2012-01-28T05:36:00

To validate....

You created a new WinForms app, you did NOT add any of your any code in any way (no assembly references). So the only thing in the solution was Microsoft stuff.

If that is correct and ONLY if that is correct....

As a wild possibility you could try turning off your firewall/anti-virus apps. Then try the new WinForms project. Sometimes they can have wild interactions with system resources including files. Shouldn't matter but worth a try before proceeding. Of course turn it back after the test.

Otherwise if it was me I would presume something had been corrupted on the system or had been uninstalled.

If WinForms requires some additional MS install (besides standard .Net) then I would uninstall it then re-install. Try the new WinForms test.

Finally I would uninstall the VS IDE and re-install. I would also see if .Net versions (1 through 4) allow for a 'fix' mode in the install/uninstall options.)

Yogesh A Rasal · Answer 2 · 2012-01-28T07:09:00

In your project code you missing some assembly file. to know which assembly file is missing in your code you expand the reference option in the solution explorer and the missing file is colored with error mark. to add this file just write click on the reference and add the references. you can add the references from computer, form .net or used project as reference for your project.

Error while trying to run project: Could not load file or assembly 'WindowsFormsApplication1' or one of its dependencies. The module was expected to contain an assembly manifest.

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0