Property accessor on object 'System.Xml.XmlElement' threw 'Object does not match target type.' exception

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Create instance of XmlDocument
2. Append processing instruction 'xml version="1.0" encoding="utf-8"'
3. Append document element
4. Inspect instance in new Data Grid

What is the expected output? What do you see instead?

System.Reflection.TargetInvocationException -->
Property accessor 'Name' on object 'System.Xml.XmlElement' threw the following 
exception:
'Object does not match target type'.

What version of the product are you using? On what operating system?

v2.1.0, Windows 8 x64

Please provide any additional information below.

#r @"c:\utils\fseye\fseye.dll"

open Swensen.FsEye.Fsi

let eye = eye
fsi.AddPrintTransformer eye.Listener;;

open System.Xml

let doc = new XmlDocument()
doc.AppendChild(doc.CreateProcessingInstruction("xml", "version=\"1.0\" 
encoding=\"utf-8\""))
doc.AppendChild(doc.CreateElement("Root"));;

Original issue reported on code.google.com by kingsley...@gmail.com on 23 Jun 2014 at 8:11

Attachments:

• ex.jpg

[GoogleCodeExporter]

Thank you for this detailed issue report! I will investigate ASAP.

Original comment by stephen....@gmail.com on 23 Jun 2014 at 11:47

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Thank you for a useful and innovative piece of software!

Original comment by kingsley...@gmail.com on 23 Jun 2014 at 12:08

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

This is "fixed" in trunk. I say "fixed" because the solution was to add a 
listener to the DataGridView.DataError event which essentially swallows these 
exceptions. I am not certain why the DGV generates these errors (it is one of 
the more complex WinForms components and does a lot of magic to determine how 
to bind a given collection), except I think it has to do with the XmlDocument 
being a collection of non-homogeneous types (they all share a common base type, 
but different specific types).

This fix will probably be released as a minor bug fix in a week or two (I am 
going to wait and see if any other little issues come up for the 2.1.0 release).

Original comment by stephen....@gmail.com on 27 Jun 2014 at 3:11

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****