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 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.
This causes conflicts with user-defined classes or namespaces that are called Utils (a fairly common name).
For example, this will not compile:
// File 1
public static void Func1()
// File 2
Utils.Func1(); // Error because Library.Utils clashes with global Utils defined in Xamarin.iOS. There is a misleading error message (The type or namespace name `Func1' does not exist in the namespace `Utils')
Library.Utils.Func1(); // This works
I think Xamarin libraries should not define any internal globally-scoped names that may clash with user identifiers.