Hi Tom,

I plan on looking at Inno the next time we do a major release. I will share my findings with you and the rest of UT.

Like many others, I am not pleased with Installshield Limited Edition or the Windows Installer technology. My real world experience with both these products has been painful and very unpleasant. We currently use Setup Factory which is a great product - but one that can't be mechanically scripted.

One of our company goals is to be able to mechancially produce a setup utility as part of an extended build process with the specs for the setup utility (files, properties, setup options, paths, shortcuts, etc.) being mechanically extracted from meta data kept in our project source code. The INI style file you shared in a previous email is EXACTLY what we're looking to generate for submission to a 'setup compiler.

Thanks again for sharing!
Malcolm

Snipped ...

If the truth be known I have not used Inno. The code that you referenced was sent to me by fellow UT participant Joe Kaufman. I have not had the need to create a setup since I was sent this code. It was stored away for future reference. I would be very interested in your feedback on using Inno. On the surface it looks like it might be a better solution than InstallShield and it is hard to be the price - its free!