5 replies to this topic

[Ralf]

Hi,
actually I´m working on a setup project which did already exist as an ISWI-project. I find the ISWI very inflexibly (put CA´s in the correct order, using properties, ....).

Until now I created my own setup projects under IS6 Prof. And I found it very smart :-)

Why should I use ISWI if I only want to copy some files in directories, make some registry entries and want to actualize the present files with newer ones???

The author of this ISWI project told me that he wanted to use the "new windows installer technique". But until now I only see disadvantages for that what I want to do.

Thanks
Ralf

[Ralf]

Sorry, I forgot to tell my used version: I´m working with ISWI 1.10.

Best regards,
Ralf

[Stefan Krueger]

I can't tell you why you want to use Windows Installer - you should look at the requirements for your setup and discuss this decision with your colleague.
Note that InstallShield Developer enables you to write your installation logic with InstallScript (similar to IS6) but the actuall install process is handled by Windows Installer. So this might also be an option for you.

[Ralf]

Stefan,
the requirements of my setups are small, I think:
- Copy files in user-directories (actualize existing files)
- Copy files in windows system directory (actualize existing files)
- Register an OCX
- Create registry entries

Is there any advantage if the installation process is handled by windows installer (instead of using IS Prof)?

Thanks,
Ralf

[Stefan Krueger]

Some advantages of MSI:
- install with elevated privileges (user's don't need to have Admin rights)
- easily deploy in corporate LAN using group policy
- auto repair
- install on demand
- aborted installs roll back to previous system state
- binary patches without additional tools
- use merge modules for redistributable OCXs (if available)
etc.

[Ralf]

Stefan,
thank you for this informations.

Best regards
Ralf