Schema support?

One advantage of the built-in XmlSerializer is that we can use xsd.exe to generate an XML schema (which I use later to generate Java classes for interop between Java and C# worlds). Does ExtendedXmlSerializer support schema generation from the classes?

[zvrba]

I have dug more into XmlSerializer and found two workarounds for “difficult” types like dictionaries: IXmlSerializable and https://docs.microsoft.com/en-us/dotnet/api/system.xml.serialization.xmlschemaproviderattribute?view=netcore-2.1 The first allows to do serialization manually, while the other allows to define the schema of custom serialization that xsd.exe will use for generating schemas.

I just wish Microsoft had established a convention for serializing dictionaries that xsd.exe recognizes, like they have for Guid.

[Mike-E-angelo]

Bummer… yeah this is a tricky problem. I myself absolutely despise the disparity between naming conventions, e.g. propertyName vs. PropertyName. So you will have all sorts of metadata around your classes to compensate, thereby polluting your classes, etc.

So for the v3 serializer, I am attempting to do something similar with HTML output. You describe your UI elements in XAML-esque components (DockPanel, Grid, etc.) and these elements then get generated into their HTML counterparts.

The same could be done with XSD? Essentially what is occurring is a mapping between objects in memory to an output in text. Essentially an object-view generation. Sounds simple until you actually have to implement it. 😛

I will keep this in mind as I go forward. There are actually 3 scenarios now:

• Serialization (default)
• HTML Generation
• Schema (XSD) Generation

The idea is that you would create a view generator provider and have it work its magic based on the object it is processing, so in your case an XsdViewGenerator, I am thinking.