We help IT Professionals succeed at work.

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

133 Views
Last Modified: 2017-04-05
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?
Comment
Watch Question

.Net Senior Developer
CERTIFIED EXPERT
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
CERTIFIED EXPERT

Author

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.
CERTIFIED EXPERT

Author

Commented:
Thanks for the help :)