Given the following XML example we could imagine a schema defining Root as containing a sequence of unbound number of choices between Type1 and Type2.
<Root>
<Type1 />
<Type2 />
<Type2 />
<Type1 />
</Root>
I am testing out migrating from the XSD.exe tool which although adds type-safety has a lot of little annoyances. The XSD tool in this case just creates within Root an array of type System.Object and you have to figure out what type of objects (Type1 or Type2) are in there. Its not completely elegant, but at least you preserve order.
The problem is when LINQ to XSD creates the objects, it defines Root as having two independent lists of Type1 and Type2. This is great in that it is type-safe, but I now appear to lose the order of the elements. I built LINQ to XSD from the source on codeplex.
Using LINQ to XSD, how can I preserve the order of these elements?