References w/ Yellow Warning Icons in VS 2010

What causes the references have yellow warning icons? Unable to debug the project due to this references issue.
How to fix this problem?

Please see attach file.

Thank you for you help.
References-with-yellow-warning-icons.doc
Queennie LAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
it usually means that the reference is using a higher version of .net than the solution is set for change the solution .net framework version and then close and reopen the solution.
0
Snarf0001Commented:
Or often it happens when someone on another computer has added the references.  Most of the ones in yellow appear to be 3rd party components.
If you either don't have them installed on this machine, or in a different location, then the icons are telling you that you're supposed to have this reference, but that it can't find the actual DLL file.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Queennie LAuthor Commented:
@David Johnson,

My apology. I just had a chance to respond to you due to weekend.

I took over this .net application to make updates. It was vb 6.0 converted to visual studio 2010. I have to clean up a bunch of forms that is not been used.

The .net framework is version 4.0. Is there higher than this?

Thank you for your help.
0
Queennie LAuthor Commented:
@Snarf0001:

My apology. I just had a chance to respond to you due to weekend.

I tried to add these missing components but no luck.

I took over this .net application. It was vb 6.0 converted to visual studio 2010.

What I am doing right now is build this old to new.
0
Queennie LAuthor Commented:
Thank you.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Development

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.