5 replies to this topic

[Lynn]

We are considering upgrading from 5.5 to 7. A year or two ago, test drove ver6 and rejected it because we allow users to install multiple versions/copies on their machines (so a user could have V7.0, V7.0EVAL, and V7.0BETA all installed). For v6, looked like I'd have to set up separate projects/guids for each release, not to mention EVAL or BETA builds (which I controlled with a simple define).

So, my question is, has this situation improved in V7? Any other big changes I should be aware of before spending days changing the script only to find out it won't work for us?

Edited by Lynn, 28 April 2003 - 23:23.

[Stefan Krueger]

Yes, this has greatly improved. Actually IMO this is one of the main benefits of version 7. It asks whether you want a new instance, or repair or modify the existing instance. It also handles updates nicely - shows a list of instances and asks which one to update.
There's a migration white paper (for version 5 and 6) at http://www.installsh...o/migration.asp
The release notes can be found at http://www.installsh...sp_readme70.asp

[prozacrefugee]

Does this still work if you change the GUID of the project inbetween iterations, or do you need to work out your own logic then?

[Stefan Krueger]

I believe the project guid must stay unchanged, but I haven't investigated this. I suggest you try it with the evaluation version.

[prasankn]

Dear Stefan,

Can you please tell me where to get the evaluation version.

So that i can work with it before buying.

But i had done Multiple installations in ISPRO 6 using guid.exe.

I had created unique uninstallation for every installation.

But the whole thing can be done easily in ISPRO 7.

Kindly guide me how to evaluate this.

regards,
prasanna N

[Stefan Krueger]

The current version is InstallShield 11.5. See http://www.installsite.biz/en/ix.htm for more information and to request the evaluation download.