Hi John, I'm excited to see the feature I suggested -- ParaffinMolds -- implemented in the new version. Will it work with the -multiple switch on? Say, I'm building a Windows Service installer for which the ServiceInstall tag must be within the same component as the service executable, with the executable identified by KeyPath=yes.

Hey John, thanks for the excellent tool. I can't believe this functionality hasn't made it into the main WiX toolset yet ;o) Anyway, it's a life-saver, thanks for providing it.

One small thing that would make it a *lot* easier to use in our build environment is if there was a way to determine whether the '-update' process has actually had to make any changes or not.

Perhaps you could make the .paraffin file identical to the source file in this case, with the same modified date and not bother update the <CreatedOn> element as you do at present? Or else set a different ERRORLEVEL exit code, or even not create the .PARAFFIN file at all if the components are the same. That way I could use the paraffin -update mode to determine whether my checked-in .wxs file is up to date or needs fixing, and make the build fail if so. It's may well be a quick change to the tool, but a very big win for anyone wanting to safely add paraffin to their automated build system! :)

By the way, if you ever get time it would be great to see this hosted on sourceforge or similar to help with bug tracking and allow others to contribute fixes to the code.

Anyway, thanks again! Ben

One of the most important technologies used at Microsoft is Event Tracing for Windows (ETW), especially

I second the suggestion/request from Ben Spiller.

After a bit of rest and relaxation, Paraffin, my tool to make managing your Windows Installer XML (WiX)