that alone seems like a good enough reason to me... you also can't set the timeout value when doing it that way
On Mon, Apr 30, 2012 at 2:17 PM, activa <[email protected]> wrote: > > jawbrey wrote > > > > I'd try having the user request the URL via Mobile Safari - just to see > if > > they are able to access it from their network or if their proxy blocks it > > or does something else strange with it > > > > also, I'd suggest not trying to load remote resources with XDocument.Load > > - > > instead I'd load the data with an async HttpWebReqeust, then load it into > > the XDocument. That gives you a lot more granular control over > > identifying > > and handling exceptions > > > > I'm already fetching the data on a background thread, so other than being > able to tell what exactly went wrong when loading the XML, what's the > advantage of using HttpWebRequest instead of XDocument.Load() ? > > -- > View this message in context: > http://monotouch.2284126.n4.nabble.com/MKMapView-crashing-on-all-my-customer-s-iPads-runs-fine-on-ours-tp4590869p4599122.html > Sent from the MonoTouch mailing list archive at Nabble.com. > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch >
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
