Clever Geek Handbook

Parsing XML files by creating an object model

I have always preferred to use XSD.exe / VS.Net to create schema, generate classes from schema, deserialize XML file in object tree to parse XML file. [Well, most of my requirements so far have made this the perfect choice.

I have a crib: the class names generated by XSD.exe are weird, meaning XSD.exe tends to keep them unique by concatenating all the previous tag names in the test.

Is there a way to tweak this? Or perhaps a tool to run on top of this?

My motive is to keep the auto-generated code intact.

Thoughts?

0


source to share


2 answers


It looks like the circuit is autogenerating which is causing the problem. I used the generation part of the XSD.exe class and the class was usually fine.



If the schema is auto-generated, it will probably need a little manual tweak to fix the crazy node names.

+1


source


I'm really starting to want an easy way to change the output of xsd.exe without resorting to the codedom hack ... it seems like a project that just "has to happen" ...



0


source






More articles:


All Articles