Bug 4332 - [Export] shouldn't require a name
Summary: [Export] shouldn't require a name
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.1.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Atsushi Eno
Depends on:
Reported: 2012-04-07 16:42 UTC by Jonathan Pobst
Modified: 2012-04-09 06:16 UTC (History)
1 user (show)

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:

Description Jonathan Pobst 2012-04-07 16:42:00 UTC
Is it possible to support:

public void MyMethod () { }

instead of just:

[Export ("MyMethod")]
public void MyMethod () { }

That is, if a name isn't specified in the [Export] attribute, we simply use the method/field/etc's name.
Comment 1 Atsushi Eno 2012-04-09 06:16:31 UTC

Parameter-less ExportFieldAttribute is still not supported as its name is for field and should not fit with a method name.