>Inno Setup is non visual, so developing the Install Package is a matter of keying in the directories, files, flags etc. into a standardized format which is well supported with their Help Files.

There is a companion product called ISTool (www.istool.org) that provides a graphical interface to Inno Setup scripts in the form of a property sheet for each script entry as well as a tree view of some of the script sections, including the files section. IMO ISTool makes working with Inno Setup scripts much easier, especially when they get to be hundreds of lines long.

>I think that ISE is probably a better product to use for New Installations where Icons, RunTime Files, Components etc. need to be installed. But for upgrades I would say that Inno Setup is a superior product because it is much easier to use and does not force you to uninstall stuff that it is picking up in the Windows Registry.

Of course you're free to adopt whatever approach works for you, but you might find it best to stick with one installer or the other for any given application over that application's life cycle. For one thing, uninstallation of an application that was installed with ISE but updated with Inno Setup might be problematic. A little testing should let you know what to expect, though.