Last post Sep 19, 2007 01:40 AM by pwhatcher
Jun 05, 2006 07:20 PM|neil58|LINK
I have a solution with 35 projects, including 2 websites. For one of the sites, I can add a web deployment project and then have a build solution work. For the other site, when the web deployment project is added, I always get an 'OutputPath property is
not set for this project' error. For both sites, I choose the Merge all outputs to a single assembly option. For the web site that doesn't work, I try to enable strong naming, but even when I take that option off, the build doesn't work.
I have tried making both deployment projects have the same options, and also removing the deployment project that works, but to no avail.
Can anyone point me in the right directions?
Jun 13, 2006 10:46 AM|JackL|LINK
I get the same build error, but only when I create a new build configuration. It works fine with the standard Debug and Release configurations, no matter what options I choose. Does anyone have any idea what could be causing this?
Steps to reproduce:
Sep 18, 2007 10:57 AM|michaelruminer|LINK
Did you ever find the issue. I have the same problem not on a web project. I do know what causes this on web projects. Web projects only have two valid configurations no matter how many you make for other projects in the solution. Only debug and release.
You can continue to use a non debug/release configuration but you will need to add the following to your rsp file and this will take care of the web projcet for you.
NOW... has anyone seen this happen on class library projects it's happening to me and all looks good?
Sep 19, 2007 01:40 AM|pwhatcher|LINK
Check that the project files actually have the configuration specified; I found sometimes it "forgets" to generate the appropriate setting into the project file although it looks like it has from the Configuration Manager.
When I went to the dropdownlist box of the project that is complaining via msbuild I found that my "Staging" configuration didn't actually exist.