Help me get off of InstallShield!!!

[Mstyler]

I am looking to stop using InstallShield. Honestly this is the first product I looked at but I don't feel I have to look any further. It is a very intuitive program and super easy to use!

:huh Anyway, what I need to do is allow the user to install multiple times from the same install to different locations. What is the simplest way to handle this? I am using the Setup Factory 7.0 DEMO if it makes a difference.

[Adam]

Mstyler,

The way it works by default is that files are installed to the location that is stored in the variable %AppFolder%. This variable has a default value and is set in the "Select Install Folder" screen. So if you know where you would like to install the files to you can set this value in script using:

SessionVar.Set("%AppFolder%","C:\\Target\\Location");

So you could leave the "Select Install Folder" screen 'as-is' and allow the user to choose a different location.

You could also remove this screen and cook up your own solution.

Are the locations pre defined? Does the user need to choose where to install to?

Adam Kapilik

[Mstyler]

I would like them to be able to use the installation disk again to do another install of the program to their own defined location. What I am really trying to avoid or at least give an option to circumvent is an uninstall. I am not worried if they can't uninstall the typical way.

For InstallShield they mentioned removing something from the registry to confuse it into thinking it was never installed.

[Steven Carr]

I would like them to be able to use the installation disk again to do another install of the program to their own defined location

So it sounds like you want to be able to install (say for example to the default locaiton, then at a later time allow them to also install to a different location.

As far as SF goes, it will not automatically uninstall the previous installation. And you can install as many times as you wish without having to uninstall first.

I think there will be an issue with the "Add/Remove Programs" section where it will only refer to the last installation - BUT the "Uninstall" available in the [Start]/Programs.... area will work for the individual installation... PROVIDED the uninstall executable is placed in a unique location for each installation (default would be common - see uninstall/settings).

[csd214]

BUT the "Uninstall" available in the [Start]/Programs.... area will work for the individual installation... PROVIDED the uninstall executable is placed in a unique location for each installation (default would be common - see uninstall/settings).[QUOTE=Steven Carr]
But that’s only true if the user selects a different %AppShortcutFolderName% on each installation (an unique %AppFolder% AND an unique %AppShortcutFolderName%).

Anyway, what I need to do is allow the user to install multiple times from the same install to different locations.

What I am really trying to avoid or at least give an option to circumvent is an uninstall. I am not worried if they can't uninstall the typical way

I’m not sure whether I understand the initial question.

Should there be several occurrences of the app on the same computer? What’s the intention? (To waste disk space….?).

If so, that’s quite the opposite of what I try to achieve, but I’m paranoid when it comes to “housekeeping”. 1) Only one occurrence of the app. 2) The user should have an easy available; and WORKING; uninstall procedure. 3) After the uninstall is executed the computer should be “100% clean”.

“100% clean” means that even the uninstaller engine and the log files are deleted (on reboot). The registry should have no traces of the app. [This is a kick to companies like Symantec, Zone Labs, Kaspersky Lab… almost everyone!].

It is possible to achieve the goal with SUF70.

[Steven Carr]

But that’s only true if the user selects a different %AppShortcutFolderName% on each installation (an unique %AppFolder% AND an unique %AppShortcutFolderName%).

Yes you are right - but you it would not be too difficult to get around this issue.

1) Only one occurrence of the app.

I have an application where i need it installed a number of times. True they are like seperate installations; I have a SF7 project setup that has all the install variables controlled by a series of constants.

[csd214]

I have an application where i need it installed a number of times.

Well, if you NEED it that way, you just NEED it. (But the uninstaller removes all occurrences?).

I’m sure you have succeeded in creating a SUF70 project to perform the setup in the way you want and need. That’s the great aspect of SUF70. You (the designer) are the boss. SUF70 obeys your orders.

[Mstyler]

I aplologize. Since I subscribed to this topic I was expecting to get an e-mail every time the topic was updated but I haven't been.


I will try to explain here in more detail. We want to do multiple parallel installs because of slow database record access time under certain data configurations in the companies software. On larger clients we sometimes need our users to install 2 or more copies of the program on one machine. This is really just a workaround for something the original programming team did not plan for. I am not looking to uninstall anything. I just want to be able to install multiple times to different folders. I am more worried about the ability to do that than being able to uninstall the silly thing. We have a top notch support team here if they need help cleaning out what was installed. What we install is really simple so there isn't much to cleaning it up. Granted a majority of the people do not need this feature. It just happens to be our bigger and more complicated clients with their mission critical data.

[Brett]

In that case, the default way that the setup works should be OK. It asks for the install location every time you run it. You could always add validation to the screen that checks the application folder location to see if the program is already installed there and then tell the user to select a different folder. OR you could automatically present the user with a unique path. i.e. The first time the setup is run on the system the app folder defaults to "C:\Program Files\DataBaseApp" and then the second time "C:\Program Files\DataBaseApp2", etc...

[Mstyler]

Thanks everyone for the super prompt assistance.

Now if I can only figure out how to create a custom screen with my own buttons and logic...