“the outputpath property is not set for this project” error

Question

I have a multi project solution in Visual Studio 2008. I just added a new Configuration called Release-VersionIncrement to the solution, specifying \"use release\" configura

Answer 1

The issue had to do with my project configuration. Here is the scenario:

Solution A references:

Project X references Project Y
Project Y

Solution B (the one I am trying to build) references:

Project X Project Z

My solution was to create a configuration with the same name for Solution A, rebuild it, and then rebuild Solution B. This fixed the problem.

Answer 2

Just had this with VS2015 Professional:

The OutputPath property is not set for project 'xxxxx.csproj'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project.

This is also multi-project juggling between debug/release and different targets. I had been fiddling with build configurations at some point and I know that can mess up VS, so I pulled them back from the repo. Still no good. OutputPath was set, there were no longer any diffs with a known good state so there was definitely something wrong with my local installation.

Opened up VS2015 installer and clicked "Repair", and voila... back to normal (so far at least!)

Answer 3

I have also seen this error when our build agent was configured to run platform "Any CPU" (with spaces as displayed in Visual Studio) rather than "AnyCPU" (one word as specified in the project file).

Answer 4

I had the same problem, I fixed it by adding missing Configurations to the project that was failing.

BUILD -> Configuration Manager ->

Under Configuration Column Add

Note: This only happened to be because I have custom configuration and newly created projects didn't have the configuration.

Answer 5

For me it was a line in the NuGet package configuration. Get rid of everything package related in your project file and see come back to life (save the edits). Than build it up again part by part. I brought it down to this line which I had to remove:

<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />

I got the problem after an update of NuGet packages (mainly FxCop analyzer stuff).

Answer 6

I've removed Platform environment variable (was BNB or smth like that). The problem is gone.