Bug 18662 - Changes to Resource.Designer file ignored
Summary: Changes to Resource.Designer file ignored
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: 1.12.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2014-03-31 08:37 UTC by Allie Miller
Modified: 2014-04-09 04:33 UTC (History)
5 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 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.

Related Links:

Description Allie Miller 2014-03-31 08:37:50 UTC
*Reported on behalf of a user*

If has been noticed that the whole solution must be manually cleaned every time a resource is changed (layout, drawables, etc). Building without cleaning cause changes to resources to be ignored. This happens whether fastdeploy is enabled or not. This makes it unclear whether a change doesn't reflect in the app because the method used was incorrectly, or because the change was ignored (no clean).

Versioning Information:
Comment 1 dean.ellis 2014-03-31 08:52:13 UTC
I've tested this on master. modifying layout files and strings.xml etc does not automatically rebuild the Resources.Designer.cs however a build does. I cannot replicate the issue where a clean is required. 

I will test on and see if I can replicate the issue on that version.

Is there a sample project available?
Comment 4 dean.ellis 2014-04-08 08:52:27 UTC
In the sample project the Main.axml is invalid. 

There is an entry which is looking for @id/svMain which does not exist.


changing this value to an id which does exist allows the project to compile and the Resource.Designer file is then updated.

So this is not a problem with the build system, but rather with the layout that is in the project.
Comment 5 Miguel de Icaza [MSFT] 2014-04-08 17:19:28 UTC

What should we do in this case?