M
MobileMan
Thought I would pass along this general comment for all those developers who
have run into this exception when attempting to build a multi-project
solution ..... The OutputPath property is not set for this project. Please
check to make sure that you have specified a valid Configuration/Platform
combination. Configuration='' Platform='AnyCPU'
We have a large solution that is comprised of over dozen related projects.
Because of some early decisions (that need to be refactored) we have circular
dependencies between several of those projects. As everyone knows, this is
generally frowned upon, although, sometimes a neccessary evil.
When choosing to "Add Reference" for a project we would normally click on
the "Projects" tab and simply choose the related project we want to
reference. For whatever reason when we completed installing VS 2008 (this is
on a box that already has VS 2005, and now has both versions installed in a
"side-by-side" setup) I tried to change some code and re-build the project.
I immediately got this exception on ALL my projects in the solution.
I noticed that I could go into various (randomly selected) classes and the
class signature ..... public partial class CCC : BBB, AAA ..... the "BBB" or
the "AAA" would be in black text instead of its usual green (this indicates
that the class or interface is no longer visible ....... a reference issue).
What makes this interesting is I checked my referencs and they all showed
"good" (meaning, none of them had the little yellow "X" indicating that
assembly is no longer visible).
The Answer: the solutin turned out to remove any reference that has
circular dependencies, and add the reference back in again, but to select the
assembly explicitly by using the "Browse" tab and surfing to the desired
assembly and selecting it (versus using the "Projects" tab and selecting it
by project name).
All of a sudden, everything compiles again and the exceptions are gone. Go
figure.
have run into this exception when attempting to build a multi-project
solution ..... The OutputPath property is not set for this project. Please
check to make sure that you have specified a valid Configuration/Platform
combination. Configuration='' Platform='AnyCPU'
We have a large solution that is comprised of over dozen related projects.
Because of some early decisions (that need to be refactored) we have circular
dependencies between several of those projects. As everyone knows, this is
generally frowned upon, although, sometimes a neccessary evil.
When choosing to "Add Reference" for a project we would normally click on
the "Projects" tab and simply choose the related project we want to
reference. For whatever reason when we completed installing VS 2008 (this is
on a box that already has VS 2005, and now has both versions installed in a
"side-by-side" setup) I tried to change some code and re-build the project.
I immediately got this exception on ALL my projects in the solution.
I noticed that I could go into various (randomly selected) classes and the
class signature ..... public partial class CCC : BBB, AAA ..... the "BBB" or
the "AAA" would be in black text instead of its usual green (this indicates
that the class or interface is no longer visible ....... a reference issue).
What makes this interesting is I checked my referencs and they all showed
"good" (meaning, none of them had the little yellow "X" indicating that
assembly is no longer visible).
The Answer: the solutin turned out to remove any reference that has
circular dependencies, and add the reference back in again, but to select the
assembly explicitly by using the "Browse" tab and surfing to the desired
assembly and selecting it (versus using the "Projects" tab and selecting it
by project name).
All of a sudden, everything compiles again and the exceptions are gone. Go
figure.