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 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.
Editing any /Resource file on Android should ALWAYS re-generate the Resource.Designer.cs file.
Now, it's easier to win on Euromillions than to get Visual Studio to realize that my .axml or /Menu/*.xml or any xml file is changed.
And there seems to be no way to firce re-generation.
Very frustrating and fragile.
## Non-engineering team preliminary cross-referencing, as a note to the Xamarin engineering teams
In addition to causes identified in bug 56082, I have also seen that Resource Designer does not get updated when I remove an item from "drawable" folder. I use Xamarin Studio.
Dean, is this an X.A build system bug? Shouldn't this regenerate as part of the IDE invoking the design time build targets? If so can you re-assign this to the appropriate component?
Thanks so much for taking the time to submit this report! I’m unable to reproduce this issue using the latest Visual Studio 15.3 preview builds.
Please attach the following to help us reproduce this issue:
-Detailed reproduction steps
-Version information (Help → About Microsoft Visual Studio → Copy Info)
-Logs (Help → Xamarin → Zip Logs (last 7 days))
-A sample project to reproduce your issue would help too
There have been updates to Xamarin Studio since I first posted this issue and lately I have not faced it. Not sure if any of the upgrades to Xamarin Studio fixed it.
Per Comment #5, I am marking this as RESOLVED-NOT_REPRODUCIBLE.