-
Notifications
You must be signed in to change notification settings - Fork 15
Escaped characters producing unexpected results #17
Description
I find that with certain XML escaped characters existing in my App.config, the transform results in the unescaped character in the resulting exe.config file. Find an example repo project here.
For example, this line in App.config:
<variable name="exceptionHeader" value="${newline}${newline}Exception Detail:${newline}" />
Results in this line within the exe.config:
<variable name="exceptionHeader" value="${newline}${newline}Exception Detail:${newline}" />
Note the conversion of : to :.
This results in errors when trying to parse the data from the exe.config. The above is an example of an NLog configuration. NLog has issues with colons (apparently even the fixed width colon), the escaped values are necessary.
Additionally newlines within an attribute are stripped. For example:
<variable name="exceptionDetail"
value="${exception: format=${exceptionFormat}: separator=
: innerFormat=${exceptionFormat}:
innerExceptionSeparator=

Inner Exception:
}" />
becomes:
<variable name="exceptionDetail"
value="${exception: format=${exceptionFormat}: separator=
: innerFormat=${exceptionFormat}:
 innerExceptionSeparator=

Inner Exception:
}" />
Note the newline disappears.
Any help in this area is appreciated. Great tool; keep up the good work!