Using/Import statement in code doesn't see reference of dll just added.

I add DLL's to my projects all the time (in C# and in VB). After employing the IDE to get the library into the project, I just type the normal "using theDLLsNameSpace" (or "Imports the DLLsNameSpace") to begin coding with that library. Nothing surprising there.

The issue I'm having today is that after adding the DLL to the project (successfully and without error) I type this:
using System.Data.SqlClient;
using System.IO;
using System.Windows.Forms;
using theDLLsNameSpace; //The problem is here

namespace XYZ
.
.

Open in new window

The good-old red underline appears with the following error (on line 4):
The type of namespace name 'theDLLsNameSpace' could not be found (are you missing a using directive or an assembly reference?)
By the way, I compiled the code myself (someone else's original code) in x86. The x86 is just because we've avoided some bugs doing it that way.

Any idea why this is happening or how to fix it?
LVL 15
David L. HansenCEOAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Elvio Lujan.Net Senior DeveloperCommented:
Verify if the theDLLsNameSpace dll is not compiled with a newer version of the Framework
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
David L. HansenCEOAuthor Commented:
That did it :)

I just rolled it back to 3.5 (and didn't use x86...not sure if that made a difference). Have you come across this before?

I'm surprised VS doesn't give a different error. It certainly knows that the reference is there and that the namespace typed in the code matches.  It's just not able to mesh the library with the solution because of conflicts between frameworks. You'd think the error would better communicate the possibility of a framework issue. Weird.
1
David L. HansenCEOAuthor Commented:
Thanks for the help :)
1
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
dll

From novice to tech pro — start learning today.