Bug 8031 - csproj with propertygroup in wrong location do not throw errors in xbuild
Summary: csproj with propertygroup in wrong location do not throw errors in xbuild
Status: NEW
Alias: None
Product: Tools
Classification: Mono
Component: xbuild ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-10-26 17:31 UTC by Curtis Wensley
Modified: 2012-10-26 17:31 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Replicates the issue for the "My-Config" configuration (4.13 KB, application/zip)
2012-10-26 17:31 UTC, Curtis Wensley

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 8031 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Curtis Wensley 2012-10-26 17:31:59 UTC
Created attachment 2803 [details]
Replicates the issue for the "My-Config" configuration

If a .csproj has a <PropertyGroup> for a project configuration is specified after the targets import, xbuild still compiles the project without error, but doesn't actually compile anything.

In contrast, msbuild will at least throw an error about the OutputPath not being set.

A fairly recent version of monodevelop put this <PropertyGroup> in the wrong place, so switching over to use xbuild may cause issues with existing projects, with no feedback on what's wrong.

I've attached a test project that has this issue. You must run xbuild with the following:

xbuild TestXBuildConfigurations.sln /p:Configuration="My-Config"