What's new ...
Version 2022 R2
•Support for Visual Studio 2022.
•Support for .NET 6.0.
Version 2021 R2
•When generating C# code, you can select .NET Core 3.1, .NET 5.0, or .NET 6.0 as target frameworks from code generation options (this adds to existing support for .NET Framework projects).
Version 2020 R2
•Code generated for XML schema wrapper libraries now provides more control over element namespaces and prefixes. New methods are available to declare or override namespaces for an element, or to append an element with a prefixed namespace. See Example: Purchase Order.
•Added support for Visual Studio 2019
•End of support for Visual Studio 2008
•Added support for Microsoft Visual Studio 2013, 2015, 2017
•End of support for Visual Studio 2005 and Xerces 2.x
•Removal of compatibility mode option for code generation
•Contains bug fixes and enhancements
Version 2010 R3
•Support for Microsoft Visual Studio 2010
•Support for MSXML 6.0 in generated C++ code
•Support for 64-bit targets for C++ and C# projects
•Enumeration facets from XML schemas are now available as symbolic constants in the generated classes (using 2007r3 templates)
Version 2009 sp1
•Apache Xerces version 3.x support added (older versions starting from Xerces 2.6.x are still supported)
•The generated mapping implementation was redesigned to support sequences and grouping. The API has not changed.
Version 2008 R2
•Support for generation of Visual Studio 2008 project files for C# and C++ has been added
•Generated MapForce mapping code in C# and Java can use readers/writers, streams, strings or DOM documents as sources and targets
•The new 2007 R3-style SPL templates have been further enhanced:
oIt is now possible to remove single elements
oAccess to schema metadata (e.g. element names, facets, enumerations, occurrence, etc.) is provided
oComplex types derived by extension are now generated as derived classes
Version 2007 R3
Code Generator has been redesigned for version 2007 release 3 to simplify usage of the generated code, reduce code volume and increase performance.
•Handling of XML documents and nodes with explicit ownership, to avoid memory leaks and to enable multi-threading
•New syntax to avoid name collisions
•New data types for simpler usage and higher performance (native types where possible, new null handling, ...)
•Attributes are no longer generated as collections
•Simple element content is now also treated like a special attribute, for consistency
•New internal object model (important for customized SPL templates)
•Compatibility mode to generate code in the style of older releases
•Type wrapper classes are now only generated on demand for smaller code