Bug 43645 - Items and properties not emitted for up to date targets
Summary: Items and properties not emitted for up to date targets
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Tools
Classification: Mono
Component: xbuild (show other bugs)
Version: 4.6.0 (C8)
Hardware: PC Mac OS
: --- major
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-08-23 02:20 UTC by Mikayla Hutchinson [MSFT]
Modified: 2018-03-15 10:40 UTC (History)
2 users (show)

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


Attachments

Description Mikayla Hutchinson [MSFT] 2016-08-23 02:20:41 UTC
MSBuild target should emit items and properties defined in ItemGroups and PropertyGroups even if the target is skipped because it is up to date. xbuild does not do this.

Here is a test case:
https://gist.github.com/b5043f541d9976f1e413f58ecfbb3613

On xbuild, it outputs the message "Included!" the first time it runs, but not on subsequent runs.
On MSBuild, it outputs the message EVERY time it runs.

Unfortunately, xbuild's own GenerateTargetFrameworkMonikerAttribute target depends on this feature. This leads to TargetFrameworkAttribute being omitted from assemblies.
Comment 1 Mikayla Hutchinson [MSFT] 2016-08-23 02:22:34 UTC
For now, I'd suggest it's easier just to hack GenerateTargetFrameworkMonikerAttribute to work.
Comment 2 Mikayla Hutchinson [MSFT] 2016-08-23 03:19:23 UTC
PR to fix the TargetFrameworkAttribute issue by working around this limitation: https://github.com/mono/mono/pull/3431
Comment 3 Marek Safar 2018-03-15 10:40:01 UTC
We deprecated xbuild and recommend using msbuild instead. Switching to msbuild will also most likely resolve the issue you reported.

Notice (2018-05-21): bugzilla.xamarin.com will be switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.

Please join us on Visual Studio Developer Community and GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs and copy them to the new locations as needed for follow-up. The See Also field on each Bugzilla bug will be updated with a link to its new location when applicable.

After Bugzilla is read-only, if you have new information to add for a bug that does not yet have a matching issue on Developer Community or GitHub, you can create a follow-up issue in the new location. Copy and paste the title and description from this bug, and then add your new details. You can get a pre-formatted version of the title and description here:

In special cases you might also want the comments:

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.

Note You need to log in before you can comment on or make changes to this bug.