Anything iOS specific about system.io or system.xml

Unity Engine
,
1

I am about to embark on setting up a class to deal with a lot of reading and writing of data to disk. I plan on using system.io and system.xml

I remember MAYBE reading, somewhere, something, that there are some limitations and things to watch out for when dealing with system.io or system.xml on iOS devices and also on the webplayer. Just thought, before investing too much time into this and running into something unexpected, could anyone point me to anything that might explain what limitations may exist with those classes on iOS and web builds? Or will everything in them work the same as they do on PC builds?

2

For iOS:
These libs aren’t included in the compressed package, so you cannot use the “micro mscorlib” option.
Furthermore these dlls will be included in the project, adding other 2-3 mb.
Expect a total of 10-15 mb file size raise.

I don’t remember anything specific for the webplayer.

3

webplayer can’t touch system.io widely as it is not allowed to touch the machine (no system.environment, severely limited system.io, no system.diagnostics, …)
System.XML works without a problem but as on iOS, it hits in at a good mb in the build size

4

I’m using System.XML extensively on iOS. Works like a charm, but as everyone else has noted, it’s got a pretty big impact on the size of your app. I’ve also had a couple of mono related problems tied to xml serialization on the device (aot compilation doesn’t like big, complex classes to serialize), but don’t know if this affects your app. I’ve just transitioned to using Sqlite in the hope that it’ll be a little more compact.

5

Could you share anything about getting sqlite into unity? I am kind of curious.