Bug 57018 - Optimize/improve @(ProjectReference) Resource Processing
Summary: Optimize/improve @(ProjectReference) Resource Processing
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 5.1
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2017-05-31 18:05 UTC by Jonathan Pryor
Modified: 2017-06-05 13:39 UTC (History)
2 users (show)

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

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 57018 on Developer Community or GitHub 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: Developer Community HTML or GitHub Markdown
  • 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 Jonathan Pryor 2017-05-31 18:05:04 UTC
Custom notices that in VS 2017, the Design Time build on their project is taking 8-12 seconds.

The build log indicates:

> Input file "Foo.dll" is newer than output file "...\R.cs.flag".

Where `Foo.dll` comes from a `@(ProjectReference)`.

Is there some way to "communicate" Resource status between Library projects and their referencing Application projects so that `<Aapt/>`/etc. processing can be *skipped* or otherwise minimized, especially if e.g. no resources have changed in the Library project?


Related(?): The `<ConvertResourcesCases/>` task is taking a long period of time, and appears to be processing `Xamarin.Android.Support.Design` and many related files: over 350 of them.

Is there any reason for `<ConvertResourcesCases/>` to be processing *Android support library* files, and anything else that doesn't actually need casing fixups?
Comment 2 dean.ellis 2017-06-05 13:39:34 UTC
I'm going to look at reworking the ConvertResouresCases to get it to be a bit more efficient. Probably by checking if a file has been modified before trying to update.