Bug 12704 - Please make ABPersonViewController.DisplayedProperties read/write
Summary: Please make ABPersonViewController.DisplayedProperties read/write
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 6.0.x
Hardware: PC Mac OS
: --- enhancement
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-06-14 17:26 UTC by Bryan Moulton
Modified: 2013-06-24 15:06 UTC (History)
2 users (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 Bryan Moulton 2013-06-14 17:26:06 UTC
ABPersonViewController.DisplayedProperties is read-only, while the ObjC implementation is read/write
Comment 1 Bryan Moulton 2013-06-14 17:31:01 UTC
My mistake, looks like this is done internally when properties are added/removed from the collection. Still, it's a bit confusing for some
Comment 2 Sebastien Pouliot 2013-06-24 15:06:37 UTC
It's a bit confusing wrt the original, ObjC, API - but it's how .NET generally works. In general you play with the provided collection, you do not replace them.