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 on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
When a file is modified in the Resources directory, the Android project runs an msbuild target to regenerate the Resources.designer.cs file. This target causes a build of the projects on which it depends. This should not happen, a file save should not cause any project to build.
This is a regression in the M4A targets.
This only appears to be an issue within MonoDevelop. Visual Studio does not exhibit the same behavour.
Fixed in master/e4e8e14e98
The fix stops dependent assemblies being re-built if we are
re-generating the Resource.Designer.cs file in MonoDevelop.
The fix was reverted because it caused some regressions.
Any update on this?
It would be great to get this fix as it can be a real annoyance on a large project. If you change things and save twice its easier to force close XS and relaunch it.
The fix for bug 10078 makes builds slower and much more verbose too, and exposes other MSBuild issues. See bug 11846 and bug 12532.
We need to figure out how to update resources without forcing a full recursive Build of all referenced projects.
Is this still a problem? Do we have a concrete test to demonstrate any problem?
Background: Library projects may contain Android resources which are "merged" with the Application project. This is in part why dependent projects were rebuilt: so that if they added/removed resources, the referencing project would get a proper "up to date" view of the resources provided by the referenced project.
The problem with the original approach was that the <MSBuild/> task was used to build the referenced projects, causing all manner of pain (see above bugs, along with many others). We have since removed explicit <MSBuild/> invocations from Xamarin.Android.Common.targets, which should be the behavior in Xamarin.Android 4.14, which means that referenced projects should only need to be rebuilt if they've actually changed (which will hopefully speed things up).
Does the removal of explicit <MSBuild/> task invocation help you? Is there something more that can be done?
Unfortunately, at a high level as long as Library projects can provide resources to the application project, and Library projects can be changed by the user, I see no way to remove the need for the Application project's resource update target to implicitly invoke/update the referenced library projects. How else do you ensure that things are kept in sync?
I'm not sure if this is still a problem. Reassigning.
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Android. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.