Release 1.1.1

Patch to v1.1.0

Fixed

Diagram Shape Bounds and Edged Waypoint properties are double now (changed in Parser, Definition, Simulator) according to the OMG standard. It was int in v1.1.0 and it blocked loading the DMN XML models with double values in boundaries due to a parser exception.
DmnDefinitionFactory ignores unsupported decision types

Added

Known types now recognize number as a typeRef in DMN XML and maps it to decimal .NET type

Changed

NormalizeVariableName replace - (dash) with _ (underscore). The name of (normalized) variable can also start with underscore
When there are multiple DI:Shapes for the same element within the diagram, the element will have multiple extensions, but the extension at Definition level will have just the last one.

Release 1.1.0

As this is a major update, it's recommended to go through the changelog and documentation.

Key additions

• DmnParser.DmnVersionEnum.V1_3ext - new version of algorithm and mapping when building the DmnDefinition from DMN XML has been added better reflecting the current Camunda Modeler generated XMLs
• Demo application DMN Engine Simulator has been added as WPF application targeting .Net 6.0 (Desktop) to demonstrate features of DMN Engine. It uses the DmnParser.DmnVersionEnum.V1_3ext when reading the DMN XML files!
• Support (and test project) for .Net 6.0, the solution is moved to VS2022

Breaking changes

• DmnDefinitionFactory - when building the definition, RequiredInputs now contain direct input requirements only (before v1.1.0, it did the recursive check through required decisions and added also the inputs required by them).
• Removed support for .Net Core 2.1
  • The library still might work when used in .Net Core 2.1 apps, however it's not being tested against .Net Core 2.1 anymore and no related fixes/updates are expected in future

Release 1.0.1

Fix of issue #11 (solved in PR #12 by @samuelsen)

Release 1.0.0

Major version release.
See the change log the documentation for details

Release 0.1.2

Support for parsing the DMN 1.3 documents (no additional functionality, just XML namespaces adjustments)

Release 0.1.1

Fixed issue with serializer in full .NET framework as described by @fgollas in PR#1.
Proxy classes are used when there are "hidden" model properties without getters.
Added the tests running on .NET framework (the v 0.1.0 code has been tested just for .NET core, where this issue not appeared).