Bug 49348 - fields in Resource.Designer.cs in Android Library are static
Summary: fields in Resource.Designer.cs in Android Library are static
Status: RESOLVED FEATURE
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: dean.ellis
URL:
Depends on:
Blocks:
 
Reported: 2016-12-08 17:47 UTC by Michal Orzechowski
Modified: 2016-12-08 17:50 UTC (History)
1 user (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:
RESOLVED FEATURE

Description Michal Orzechowski 2016-12-08 17:47:24 UTC
In Android application project in Resource.Designer.cs fields are const, eg.
public const int play = 2130837597;

but in Android library project fields are static, eg.
public static int play = 2130837507;

It would be great when will be const in both project types.

This is code about it:
https://github.com/xamarin/xamarin-android/blob/cycle9/src/Xamarin.Android.Build.Tasks/Utilities/JavaResourceParser.cs#L86

It has been done intentionally?
Comment 1 dean.ellis 2016-12-08 17:50:05 UTC
It was done on purpose. 

We need to be able to update the values in the library (it might have older/incorrect id values). which is why static was used.