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.
For example, void SetCurrentItem (int p0, bool p1)
For cases like this, we should try to fix these names, since it would allow better use of our C# named parameters feature.
This won't happen until we release a major version-up release *that can break API compatibility*.
I doubt many customers are using named parameters with existing p0, etc. arguments. Why would someone? They are cryptic.
I don't care about parameter name changes, but it's not (only) about parameter names but about *type* names which are used in generated *EventArgs*. They do break ABI compatibility significantly.
We ended up to bring those parameter names in support-v* bindings. The binding keeps ABI-compatibility members with [Obsolete] attribute to not break API.
It will be available in the next alpha version.