The problem is that I get a XamlParseException when I try to run this XAML. I have determined it is when it gets to the dq:DataColumn element. It seems like this is only happening when I have a property that then has a collection and then several items in the collection that I am getting this issue.

Has any encountered anything similar? I am try to achieve this all in XAML declaratively.

Thanks for your response. The DataColumns property on the DashbboardTableQuery object has a field that is a new List<DataColumn>(). I would think this would satisfy both of the requirements for the Xaml to work. One other caveat is that the object model is coming from a WCF Service via a Web Reference.
–
mattduffieldMar 16 '10 at 14:06

@mattduffield: If it really is a "field" change it to a Property. For your xaml to work it really should be a read-only property or at least a Property that has the collection initialised ready to have items added.
–
AnthonyWJonesMar 16 '10 at 14:12

It is a property with the field that is being wrapped defaulted to a new List<DataColumn>(). Sorry for the confusion. I agree that this could be a read-only property.
–
mattduffieldMar 16 '10 at 14:20

@mattduffield: Then so far I can't see anything wrong, can you provide more details regarding the exception you are seeing?
–
AnthonyWJonesMar 16 '10 at 15:08

It turns out that it was an issue with creating the WCF Service Reference. It will by default serialize List as Arrays. You can change this behavior but that still doesn't help us on the Xaml side of things since it wants a ready to use initialized collection.
–
mattduffieldMar 16 '10 at 22:55