Error Solving

Question

0.00/5 (No votes)

See more:

i developed a WPF application and i encountered this problem

MSIL

Error   1   Unknown build error, 'Could not load file or assembly 'Microsoft.Windows.Design.Extensibility, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)'   photo

can anyone help me in how i can solve that...?

Posted 30-Nov-10 15:03pm

Yasser El Shazly

Updated 30-Nov-10 18:36pm

Tarun.K.S

v3

Add a Solution

Comments

Dave Kreskowiak 30-Nov-10 21:18pm

Without further information, like the COMPLETE error message and stack trace, it's impossible to say.

Tarun.K.S 1-Dec-10 0:42am

The probable case might be with the references that you have referenced.Do referencing with correct versions.

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)

Abhinav S · Answer 1 · 2010-11-30T18:38:00

Solution 2

Make sure you have added a reference to the right dll.

Posted 30-Nov-10 18:38pm

Abhinav S

ROGDEV · Answer 2 · 2010-11-30T15:33:00

Solution 1

Sounds like it could be a discrepancy between what you've referenced and the .Net version installed on the target machine. Try re-referencing the libraries and/or reinstalling the .Net framework.

Posted 30-Nov-10 15:33pm

ROGDEV

Comments

Yasser El Shazly 1-Dec-10 0:40am

how can i do that..?