Hi and thanks, I was thinking the same; that it was something outside this block that caused the problems. However, I don't have any more CDATAs or "]]>" in this WiX file. This file only contains a fragment, and I have another xml containing the <product> block. This file does not contain any CDATA either. The program is compiled and msi created using SCons, so there is a SConstruct file starting this. Unless this adds any extra outer xml behind the scenes there is no CDATA to be seen.
Everything works fine when removing the condition line. You say that I probably don't need the CDATA. Do I get access to the parameters VersionNT and Version9X outside this? I'm sorry if I ask any stupid questions, but I'm new to WiX and haven't used CDATA before neither.. John Vottero wrote: > > I don't think you need the CDATA for your condition. Conditions are > usually wrapped in CDATA because they often contain < and > characters. > > That being said, are you sure that the problem is actually in the > fragment that you posted? Your CDATA looks fine to me, I'm thinking > that maybe something else is messing up the parsing and makes candle > think that you have a "]]>" in your CDATA. Do you have any other CDATAs > in this WiX file? If you remove that condition line, does it compile? > -- View this message in context: http://www.nabble.com/GDI%2B-MergeModule-tf4316091.html#a12393572 Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
