Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
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?
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.