Last post Jan 07, 2009 01:28 PM by SKT_01
Jan 07, 2009 09:34 AM|twilson|LINK
I've started an open-source project at http://sourceforge.net/projects/plistdotnet
It allows data (DataSet/DataTable/DataRow objects), custom classes (public properties of serializable classes) and generic collections (such as Dictionary<Tkey, Tvalue> and List<T>) and standard arrays (object) to be passed to my "PlistDocument" class
and a valid XML Property List is generated.
A Property List (plist) is the simplest and most lightweight way of processing external data on the iPhone/Mac.
It has been released under a BSD license to give the most freedom.
Any help with testing, documenting would be greatly appreciated, as I really want to help enable companies fully exploit the iPhone platform, and this will help as a quick way to adapt existing .net application data feeds into something consumable by the
iPhone, without the need for a completely separate disconnected datastore.
Jan 07, 2009 10:09 AM|SKT_01|LINK
Who needs this?
Jan 07, 2009 11:00 AM|twilson|LINK
Arguably anyone who would like to expose data held in a .net applicaiton through a web service with minimal effort.
Pass in your object and it spits out a valid property list based on the available public properties. Download it and have a look at the documentation and you might get an idea of who would find it useful.
A number of people on Apple's developer forums certainly posed this exact problem. They wanted the easiest way to get the data out of .net, and the simplest way of getting it into something usable (Key-Value Coding) on the iPhone side of things.
You'd be surprised!
Jan 07, 2009 01:28 PM|SKT_01|LINK
Thank you very much for the explanation. I know nothing about native iPhone applications and I had never read that developers who want to consume a SOAP web service in a native iPhone application need a plist.