Bug 22069 - Resource not updating
Summary: Resource not updating
Status: VERIFIED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: 5.2
Hardware: PC Windows
: Normal normal
Target Milestone: master
Assignee: Greg Munn
URL:
Depends on:
Blocks:
 
Reported: 2014-08-13 13:29 UTC by Leonardo
Modified: 2015-01-20 07:38 UTC (History)
5 users (show)

Tags:
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 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.

Related Links:
Status:
VERIFIED FIXED

Description Leonardo 2014-08-13 13:29:37 UTC
Hello,

I updated my Xamarin Studio with version 5.2, and my new updates in layout not
 creating in Resource.Id.

I saw this topic(21549), but not have answer:
"Resource.designer.cs file is not recreated when modify/add layouts so device
and code not recognize new resources. 
Cleaning/Building project no errors are showed, but new layout is missing in
the code. I'm getting this problem after update to version 5.1.0. Now I use
5.1.4 but not work for me. I'm not sure it's an error of my project or a bug of
Xamarin Studio because no errors are showed."

P.s: My project was started long ago in another version of Xamarin.
Comment 1 Leonardo 2014-08-18 09:08:31 UTC
I'm waiting for a solution and my client too...

Anything?
Comment 2 Rajneesh Kumar 2014-11-05 09:11:22 UTC
We have checked this issue but not able to reproduce this. We have try to reproduce this issue with the help provided in bug description. We have followed the steps below:

1. Create an android application in XS.
2. Open Main.axml, go to design view
3. Go to ToolBox and drag "Button" and "ImageView" control on it.
4. Click on Button go to property and change it's id to "TestButton".
5. Click on "ImageView" go to property and change it's id to "TestImage".
6. Save the project and open "Resource.designer.cs"
7. Observe that Resource ID are created.
8. Go to Layout, make any changes to the control's ID, save the project.
9. Observe that Resource ID are updated in "Resource.designer.cs".

Screencast: http://www.screencast.com/t/Te4AkZXVJMm

Could you please check this issue with the latest Xamarin builds and please let us know if you are still getting this issue.

Environment Info:

=== Xamarin Studio ===

Version 5.5.3 (build 6)
Installation UUID: a7e29e93-6348-4126-9ebc-b2777c96a552
Runtime:
	Microsoft .NET 4.0.30319.18408
	GTK+ 2.24.22 (MS-Windows theme)
	GTK# 2.12.26

=== Xamarin.Android ===

Version: 4.18.1 (Business Edition)
Android SDK: E:\android-sdk
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		4.5    (API level 21)
Java SDK: C:\Program Files (x86)\Java\jdk1.6.0_39
java version "1.6.0_39"
Java(TM) SE Runtime Environment (build 1.6.0_39-b04)
Java HotSpot(TM) Client VM (build 20.14-b01, mixed mode)

=== Build Information ===

Release ID: 505030006
Git revision: fbe3e9453daf6a3bb9a9709ed22bec35f7c9056b
Build date: 2014-10-23 13:11:11-04
Xamarin addins: e44add2b39de4dd57c0742bb2e620dfad84c64c6

=== Operating System ===

Windows 6.2.9200.0 (64-bit)
Comment 3 Leonardo 2014-11-06 04:38:04 UTC
This problem has solved in a update after this post.
Comment 4 Shruti 2015-01-20 07:38:20 UTC
As per comment 3, I am closing this issue.