> Hi,
>
[quoted text clipped - 13 lines]
> I'm googling, but having trouble finding a clear answer/program flow to
> this.
Yes it is possible, the object you end up with would probably have
collection or ArrayList as a property or an array. In your class
definition, you can specify, through attributes, how things should be
deserialized.
Good luck.
Chris
David Browne - 31 Aug 2006 20:08 GMT
sherifffruitfly wrote:
>> Hi,
>>
[quoted text clipped - 18 lines]
> definition, you can specify, through attributes, how things should be
> deserialized.
DTD is old and everything in .NET is based on XML Schema. If you can
convert your DTD to an XSD, then you can use XSD.EXE to generate a .NET
class definition to de-serialize instances.
GotDotNet User Sample: Dtd2Xsd 1.1
http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=54358B80-
1324-49E9-821B-A08911356AD7
David
sherifffruitfly - 31 Aug 2006 20:33 GMT
> DTD is old and everything in .NET is based on XML Schema. If you can
> convert your DTD to an XSD, then you can use XSD.EXE to generate a .NET
> class definition to de-serialize instances.
>
> GotDotNet User Sample: Dtd2Xsd 1.1
> http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=54358B80-
1324-49E9-821B-A08911356AD7
I knew dtd was old, but didn't realize it was substantially easier to
do what I wanted with a schema - i'll look into the dtd2xsd
conversion/xsd.exe process you mention - thanks!