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.
I came across interfaces named IButtonListener, IJoystickListener, IStreamConnector etc. (com.zeemote.zc.event in Zeemote SDK, http://www.zeemote.com/). When they are mapped to managed interface, they become IIButtonListener, IIJoystickListener and IIStreamConnector and so on, which does not make sense.
I can fix the naming itself, but there is a blocking issue: we somehow premises that Java interfaces are *never* prefixed (actually the premise is kind of worse: "there won't be any type that has IXxx and Xxx"). When there is ISomeInterface which contain some consts, there will be C# ISomeInterface *class* that is to contain corresponding managed fields. But the name is for the interface itself (when this issue gets fixed) and there is no room for the abstract class.
Fixed. In case it gets stuck by name conflict explained above, metadata fixup should be available.