Release 1.3.0

Release 1.3 is fully backwards compatible with 1.1 and 1.2 and has two changes:

1. Supports CDATA xml nodes and therefore solves issue #2 "Type System.Xml.XmlCDataSection is not supported".
2. Ignores COMMENT xml nodes and therefore solves issue "Type System.Xml.XmlComment is not supported".

Release 1.2.1

Release 1.2 is fully backwards compatible with 1.1 and has two major changes:

1. a major overhaul of the tree walking algorithm, which now can take every xml you can throw at it. This solves most, if not all, the bugs of the previous release.

2. an implicit type conversion for string, int, decimal, double and bool. So now you can parse an xml and directly use its numbers or true/false values (see readme for examples).

Version 1.2.1 also has better behaviour when converting: if the xml content is invalid (say, if you try to use "lalala" as bool) then you get a ValueConversionException.

Release 1.2

Release 1.2 is fully backwards compatible with 1.1 and has two major changes:

1. a major overhaul of the tree walking algorithm, which now can take every xml you can throw at it. This solves most, if not all, the bugs of the previous release.

2. an implicit type conversion for string, int, decimal, double and bool. So now you can parse an xml and directly use its numbers or true/false values (see readme for examples).

Release 1.1

This is a production-ready release.

The binary is a Release/Any CPU build. The assembly was converted to .Net Standard and tests to .Net Core to make the assembly portable.

There is a pending issue, see Release 1.

Release 1

This is the first production-ready release.

The binary is a Release/Any CPU build.

An issue (to be solved in the next release) is on handling non-root non-nested lists (multiple nodes with the same name). For example:

<City>
  <Name>Wilen bei Wollerau</Name>
  <Gemeinde>Freienbach</Gemeinde>
  <Street name="Wolleraustrasse" />
  <Street name="Hungerstrasse" />
  <Street name="Rebmattli">
    <PostCode>8832</PostCode>
    <HouseNumber>10</HouseNumber>
    <HouseNumber>12</HouseNumber>
    <HouseNumber>14</HouseNumber>
  </Street>
</City>

The HouseNumber nodes generate an error. If the xml is changed to e.g.:

<?xml version="1.0" encoding="utf-8" ?>
<City>
  <Name>Wilen bei Wollerau</Name>
  <Gemeinde>Freienbach</Gemeinde>
  <Street name="Wolleraustrasse" />
  <Street name="Hungerstrasse" />
  <Street name="Rebmattli">
    <PostCode>8832</PostCode>
    <HouseNumbers>
      <HouseNumber>10</HouseNumber>
      <HouseNumber>12</HouseNumber>
      <HouseNumber>14</HouseNumber>
    </HouseNumbers>
  </Street>
</City>

...then it's fine.

Alpha 1

This is the first pre-release. It works in most cases. The binary is a Release/Any CPU build.