Getting Problem in adding Refrence

Question

0.00/5 (No votes)

See more:

Hi Friends......

I have added a reference of a System.Windows.Forms.Ribbon.dll.
but when i build or Execute code then reference is removed
and compiler shows error Are you missing assembly reference.

When i check in Solution Explorer its reference is shown there.
but it is showing this problem.

When i delete this Reference and again add then it remove errors from error list.
but, again when i run it is again showing same Problem.

Posted 17-May-12 2:00am

Varinder Raii

Add a Solution

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)

Wendelius · Accepted Answer · 2012-05-17T02:04:00

Solution 1

Quite similar problem here http://stackoverflow.com/questions/8791606/when-compiling-app-it-removes-references[^] perhaps the same solution helps in your case.

Posted 17-May-12 2:04am

Wendelius

Comments

VJ Reddy 17-May-12 8:18am

Good reference. 5!

Wendelius 17-May-12 8:35am

Thanks

Pete O'Hanlon · Accepted Answer · 2012-05-17T02:06:00

Solution 2

When I've seen this type of problem in the past, it's normally down to project configuration, specifically, targetting the wrong version of the .NET runtime. Make sure that you have set the target framework to .NET Framework 4 or .NET Framework 4 Client Profile.

Posted 17-May-12 2:06am

Pete O'Hanlon

Comments

VJ Reddy 17-May-12 8:18am

Good answer. 5!

Pete O'Hanlon 17-May-12 8:29am

Thanks. I was hit with this one once when someone on my team decided to move the project from .NET 4 to .NET 3.5.