Version 1.0.0

Bug fix for issue #9 and bumping version to 1.0.0

Version 0.2.10

Bug fix for issue #5

Insert* transforms continue to be a pain. Previously the I would try and use InsertAfter as much as possible.
But this is causing issues when inserting an element a after another element b that hasn't yet been inserted -
we write the deletions and insertions out to the patch in reverse order to help get an accurate 'Locator'.
Now the insert logic should prefer 'InsertBefore' where possible, with a fallback to 'InsertAfter'.

Version 0.2.9

Bug fix for issue #4

Web.config files (and generally XML) are case-sensitive. But when building the XTree the element and attributes' names were being converted to lower case.
These names were then being used to construct the XPath expression in transform attributes (InsertBefore, InsertAfter etc).
I've removed the conversion to lower case and added tests for case sensitive comparison.

Version 0.2.8

Further changes to support edge cases - handling both inserts and del…

…etes using index traits.

Version 0.2.7

Bug fix for issue #2.

Adding support for the case where a element's unique attribute trait will change with a transformation and there are also changes to its child elements (particularly inserts with absolute xpath values).

Version 0.2.6

Bug fix for Issue #1.

Null exception being thrown in the case when an element is removed from the target config.
Added tests for removal of elements and attributes.

Version 0.2.5

Includes a bug fix for missing xdt:Locator values on single child nodes, where a second child is being inserted in the transformation.

Version 0.2.3

Added support for InsertBefore and InsertAfter transforms

Version 0.2.2

Minor bug fixes and improvements to XDT output.

Version 0.2.1

* Improve the selection of an attribute for the xdt:Locator attribute.

XdtWriter now tries to choose a unique attribute that also hasn't changed between the two trees.