John Hall wrote:
Should the WiX preprocessor give an error if there is a statement that it does not recognise? I just spent some time tracking down a problem, which eventually came down to me using <?elsif ?> rather than <?elseif ?>. An error message saying <?elsif was not recognised would have been useful.
I would have assumed so but there's a comment in the current preprocessor code that says:
default: // unknown processing instructions are currently ignored break;Seems ugly to me and by "currently," I'd say it's open to a nicely-worded feature request.<g> I assume it's there for extensibility but extensibility was added via preprocessor extension which requires a prefix...
-- sig://boB http://joyofsetup.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 [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
