There's still some work to be done: I couldn't find the resource strings in ReferenceSource (maybe someone else can find them), unit tests need to be added, and the coding style of the copied code is really old fashioned, maybe that could be cleaned up as well.īefore I spend more time in this effort, Is this modification (actually, just re-adding some classes) something that the. The generator uses one of 3 designs to generate the XSD (consult xfront. The generator will try to use a smart approach to figure out the data type (you can always refine it after). Simply copy-paste OR upload your XML document and let the generator figure out the rest. After adding a lot of nullable annotations and null checks I now have a version of XML.Serialization that builds with these old/new types included. Generates a XSD (XML Schema) from a XML file. Of course, this caused a small cascade of other missing types, and I added them as well. So I forked dotnet/runtime and copied the missing type from.
This didn't work because one type was missing: XmlCodeExporter. I found the source code on ReferenceSource, and tried to build it against. Am I heading in the right way?īecause our team also has a need for for xsd.exe (or a similar tool) I went looking what is needed to revive xsd.exe. As a prerequisite, I've made some changes to XML.Serialization. TL DR: I'm trying to get xsd.exe to run under.
