When I try to compile my project from x86 debug mode in Visual Studio 2008. I am getting this error. When I looked at the property group of the project that complained, I see output path is set.
Here is the property group section for that .csproj file
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|x86' "> <DebugSymbols>true</DebugSymbols> <OutputPath>bin\x86\Debug\</OutputPath> <DefineConstants>DEBUG;TRACE</DefineConstants> <BaseAddress>285212672</BaseAddress> <FileAlignment>4096</FileAlignment> <DebugType>full</DebugType> <PlatformTarget>x86</PlatformTarget> <ErrorReport>prompt</ErrorReport>
Can any one shed the light on this?
NOTE: When I compiled this Debug and Any CPU it worked.
UPDATED: Error 1 The OutputPath property is not set for this project. Please check to make sure that you have specified a valid Configuration/Platform combination. Configuration='Debug' Platform='x86'
This question is tagged with
~ Asked on 2012-01-31 20:54:48
I had exact same error after adding a new configuration via ConfigurationManager in Visual Studio.
It turned out when the 'Production' configuration was added for the whole solution (and each project) the OutputPath element was not added to the .csproj files.
To fix, I went to the Build tab in project properties, changed OutputPath from
\bin\Production (deleted trailing
\) and saved changes. This forced creation of the OutputPath element in the .csproj file and the project has built successfully.
Sounds like a glitch to me.
~ Answered on 2015-07-29 14:42:36
You can see this error in VS 2008 if you have a project in your solution that references an assembly that cannot be found. This could happen if the assembly comes from another project that is not part of your solution but should be. In this case simply adding the correct project to the solution will solve it.
Check the References section of each project in your solution. If any of them has a reference with an red x next to it, then it you have found your problem. That assembly reference cannot be found by the solution.
The error message is a bit confusing but I've seen this many times.
~ Answered on 2012-01-31 22:01:27