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 for Bug 35893 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
I've started using Gendarme (mono-tools) for some static analysis to improve my project code with Xamarin and noticed that the generated code in the Android Resource.Designer.cs is using a bad practice by making all the generated values `public const int`.
The rule that marks it as a bad practice is Gendarme.Rules.BadPractice.AvoidVisibleConstantFieldRule.
- Change the access to internal (`internal const int`) to prevent external assemblies from accessing
- Change to `public static readonly` as Gendarme suggests so the assemblies that reference a value don't have to rebuild on changes.
- Add a accessor level option to an android project/designer file.
The best practices are subjective.
I am not sure if it is by design that values in designer files are `public const`, I will request engineering team to comment on this.