Project Reference added to one of the projects in the same solution appears broken in another solution
Posted
by
CSharpLearner
on Stack Overflow
See other posts from Stack Overflow
or by CSharpLearner
Published on 2011-01-11T09:50:34Z
Indexed on
2011/01/11
9:53 UTC
Read the original article
Hit count: 169
visual-studio
|projects-and-solutions
I have couple of solutions.
In the first solution I have many projects. One of the project named 'A' has a project reference of another project 'B' of the same solution.
In second solution, the project 'A' is added but not the project 'B'.
Both the solutions build successfully.
However, in second solution, reference of B added in the project A, appears broken.
Why?
Now, in first solution, instead of adding Project reference of B into A, i simply add a 'file reference' of B's DLL (which is copied at the common output directory created for all the projects) into A. Now the reference appears broken in both the solution even though both the solutions are built successfully.
May I know what should I do when I have such a scenario?
© Stack Overflow or respective owner
