Thanks Rob, that worked great.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-New-Lines-in-Text-Fields-for-Custom-WiX-Extension-Doesn-t-Work-tp5214598p5217423.html
Sent from the wix-users mailing list archive at Nabble.com.
-
In your table's columnDefinition set the escapeIdtCharacters attribute to
"yes".
On Wed, Jun 23, 2010 at 4:54 PM, jnewton wrote:
>
> Looks like when posting, my xml character codes went away. Here is a
> screenschot of the codes.
>
>
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.co
Looks like when posting, my xml character codes went away. Here is a
screenschot of the codes.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n5215703/New_Line.png
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-New-Line
I have developed a custom extension and have found that if I use
newline/return character xml codes in text fields, WiX incorrectly generates
the temporary IDT files. Thus when WiX is trying to apply the IDT files to
the MSI, it fails. For example, suppose I have the following custom table:
4 matches
Mail list logo