2 replies to this topic

[Xitch13]

This is probably a dumb question, but is there any way to build my distributal as a .msi file in IS Pro 7?

I know we can probably not do this since Pro 7 needs to include its framework. However, I have a customer who wants to distribute my installer in an Active Directory 2003 enviroment and can't copy the executable. I've explained it's probably his security set wrong, but he's unwilling to change anything on his end. He doesn't understand why when his inhouse guy is using IS Developer he can build a .msi file, and I can't using IS Professional.

An answer and any thoughts would be most appreciated.

[Stefan Krueger]

For Active Directory deployment you would need a Windows Installer based setup (i.e. an .msi file). Windows Installer is a completely different technology than InstallScript. InstallShield Professional 7 cannot create .msi file. Starting with version 9, InstallShield has combined the "InstallShield Professional" and "InstallShield Developer" product lines, so using the latest version you can build either InstallScript or Windows Installer setups. However there is no clean way to convert between the two project types. In other words: you would have to start from scratch.
One possible workaround would be a "warpper msi". Windows Installer setups can call executables at install time. So you could create a .msi file that would not actually install anything, but only launch your exe. You can find links to such wrappers at http://www.installsi.../msi/admins.htm . The Gordan Mills web site listed there even has a "Universal Wrapper" that may help you to solve your problem without changing your setup and without purchasing an MSI tool.

[Xitch13]

Just to give an update here. I did try to wrap my self-contained executable in an MSI file and just launch it. Unfortunately, it would call the executable, just not allow the IS framework to start up. I'm not sure if it was MSI preventing another framework to use its resources or if IS framework will not launch when MSI is running.

I eventually just drove to the customer's site, and built the installer again using their version of Developer. I am now very glad my predecessor here decided to send the company down the Professional route. Everything I wanted to do from checking versions in the registry to finding and deleting a file were ten times harder. Of course, you can use InstallScript to do it, but the you can't build it as an MSI!!