Tallow Secrets (?)

I'm deep into wix right now and I recently found out how to successfully use tallow. Who knew that “>>“ will append all the information from the console output to an actual file? I didn't. Here is what I have been doing to test tallow results:

C:\setups\wix> tallow -d . -nologo

The problem with my results was that the output was actually written to the console window. I looked everywhere on how to get this information into my own wxs file. I searched hi and low on the web and nobody described how to do this. I found a link on the web that shows how some other tool is used and after investigating the code on the page, I saw that this tool has an undocumented feature to output all the information into a file by simply using two “>“ signs followed by a filename. I modified my test to use this for tallow as such:

C:\setups\wix> tallow -d . -nologo >> output.wxs

Shazang! Bah-da-bang!

I assume that “>> [filename]” works with any console app now that I see it can be used with tallow. Yeah, ok, so this is probably globally-known knowledge, but I just got here so bear with me. :) I now realize that tallow saves me a lot of work! However it is a bit late to save me a whole lot. I say this because I actually wrote my own utility that recursively loops through directories and create <Feature /> elements, <File /> elements, and <Directory /> elements. My utility offered filtering options very similar to the ones that tallow offers. My solution is nowhere near as robust as tallow, but it got the job done that I needed it to. I realize now that I was trying to reinvent the wheel, but tallow isn't very well documented in the Wix.chm yet and I had no idea that it did all this.

I'm now going to be changing my wix setup scripts to use tallow, as it has lots of options that my solution did not offer (extracting com crap, applying various attributes, extract registry crap, etc...).

Print | posted on Monday, August 15, 2005 3:14 PM