The type or namespace name 'NAMESPACE' could not be found (are you missing a using directive or an assembly reference?)

Question

1.00/5 (1 vote)

See more:

I keep getting this error when I build my project. The project was converted to 2.0 from 1.1. The NAMESPACE in question exists and is added to the solution. The unit reporting the error is Global.asax.cs sitting an App_Code folder. Also another 2 units in the same folder are reporting same error about same NAMESPACE plus another one. Again the assemblies are added as references to the project.

Thanks

Adrian

Posted 1-Feb-11 9:40am

Nairdaj

Updated 1-Feb-11 9:49am

Henry Minute

v2

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)

dasblinkenlight · Answer 1 · 2011-02-01T12:20:00

For what it's worth, I remember seeing the same symptoms when the target framework of the referenced assembly was ".NET Framework 4", but I was referencing it from a class library with the target of ".NET Framework 4 Client Profile". Once I changed the target framework of my class library to match that of the referenced assembly, the problem disappeared.

Henry Minute · Answer 2 · 2011-02-01T09:55:00

Solution 2

Take a look at the Note part in this page[^] from MSDN.

Could this be the cause of your problem?

Posted 1-Feb-11 9:55am

Henry Minute

Comments

Nairdaj 1-Feb-11 16:53pm

Nope, I tried boths ways, using projects and pointing directly to files. None of them are working.

Henry Minute 1-Feb-11 16:54pm

OK.

Worth a try though. :)