Hi all,
I really like the tool and have used it successfully for a C# project. I have a point of feedback regarding the tool xsd2Code, that could possibly be interesting to improve the tool even further...
In attachment, you will find 4 XSD-schemes, that belong together. The main scheme is the DIVArchiveWS.xsd-file. In Microsoft Visual Studio, I right-clicked on this file to run the xsd2Code tool and this generated the DIVArchiveWS.designer.cs-file, with the namespace DIVArchive, that I then used in my project. I saw the tool was smart enough to use Inheritance.
One small problem : in the inherited classes, it also generated Serialization methods. This is not needed, because they are exactly the same as the ones implemented in the base class. This did not break the functionality of the code, but as it is redundant, it caused warnings.
Maybe it is a good idea to, in this case, omit these methods in the inherited classes?
Kind regards,
Joachim Ally
I really like the tool and have used it successfully for a C# project. I have a point of feedback regarding the tool xsd2Code, that could possibly be interesting to improve the tool even further...
In attachment, you will find 4 XSD-schemes, that belong together. The main scheme is the DIVArchiveWS.xsd-file. In Microsoft Visual Studio, I right-clicked on this file to run the xsd2Code tool and this generated the DIVArchiveWS.designer.cs-file, with the namespace DIVArchive, that I then used in my project. I saw the tool was smart enough to use Inheritance.
One small problem : in the inherited classes, it also generated Serialization methods. This is not needed, because they are exactly the same as the ones implemented in the base class. This did not break the functionality of the code, but as it is redundant, it caused warnings.
Maybe it is a good idea to, in this case, omit these methods in the inherited classes?
Kind regards,
Joachim Ally
