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 herenamespace XYZ..
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
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.
David L. Hansen
ASKER
Thanks for the help :)
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
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.