Namespace becomes unavailable on build

Question

Possible Duplicate:
Visual Studio 2010 suddenly can’t see namespace?

I'm adding a reference to project2 from project1. They are in the same solution. I can access the namespace of project2 from within project1 at this point. However, once I build the solution or project1, project2 namespace is no longer available in project1. I've restarted VS2010 but that didn't help.

Any ideas on what is causing this and how to fix it?

I noticed that Intellisense sometimes differs from compilation. First guess would be to check the projects' .net versions. — devio, Dec 13 '12 at 22:04
Are the binaries for Project2 being copied to the Project1 output folder? More specifically, are the Project2 binaries available to Project1 at runtime? — RJ Lohan, Dec 13 '12 at 22:04
@RJ, I haven't done anything to modify that and not sure where I would. So I'm not sure what the answer is. — 4thSpace, Dec 13 '12 at 22:05
@4thSpace - right click the project reference for Project2 and look at its properties. Copy Local = True usually helps. — RJ Lohan, Dec 13 '12 at 22:06
Probably. Although they're dealing with a Winform app. I'm not sure how many app configurations this happens with. — 4thSpace, Dec 14 '12 at 00:05

score 2 · Answer 1 · answered Dec 13 '12 at 22:47

2

For this to work, I had to change the console app from '.NET Framework 4 Client Profile' to '.NET Framework 4'.

answered Dec 13 '12 at 22:47

4thSpace

43,672
97
296
475

score 0 · Answer 2 · answered Dec 13 '12 at 23:01

0

And after you added the reference to 'project2', you did add a 'using project2;' statement?

answered Dec 13 '12 at 23:01

Norman Skinner

6,729
1
19
22

Namespace becomes unavailable on build

2 Answers2