In general, Java setters/getters will be transformed into C# properties where possible. As you noticed, some of them don't - this has to do with the semantics surrounding the getter/setter. For example, sometimes a Java getter/setter may be overloaded to accept different parameters - in that case the Java method will be mapped as a C# method and not a property.
I'm not to sure if you can (or should) force the Java getter to a C# property in this case. Maybe Jonathan or Eno can shed some light here? On Tue, Sep 18, 2012 at 11:43 AM, Jeremy A. Kolb - ARA/NED <[email protected]>wrote: > I’ve noticed that not all of the Get/Set methods in jars become > properties. Sometimes none of them do and sometimes only the Get or Set > gets mapped. How do I ensure these methods get mapped to C# properties?** > ** > > ** ** > > Jeremy**** > > _______________________________________________ > Monodroid mailing list > [email protected] > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid > > -- http://www.opgenorth.net
_______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
