Hi mono list, I find that when I catch exceptions from XML deserialisation code, they don't contain the stack trace of my calling code, so it's difficult to determine exactly what's happened.
Is this a known issue? Is there a better workaround than catching and re-throwing the exception? Thanks, River System.Xml.XmlException: Document element did not appear. file:///home/ubuntu/out/20151202_191505153.xml Line 1, position 1. at Mono.Xml2.XmlTextReader.Read () [0x00000] in <filename unknown>:0 at System.Xml.XmlTextReader.Read () [0x00000] in <filename unknown>:0 at System.Xml.XmlReader.MoveToContent () [0x00000] in <filename unknown>:0 at Mono.GeneratedSerializers.Literal.GeneratedReader.ReadRoot_orders () [0x00000] in <filename unknown>:0 at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&) at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
_______________________________________________ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
