I have Endnotes version 10, one of the Dependences is 3.1 installer engine. i don't want to repackage the application since it's already a MSI. how can i get windows installer 3.1 to install before launching the application.
What i have tryed. i try making a wrapper but the only choice i get is ver 2.0 of the install engine. also i made a test project and compile it with windows installer 3.1 and modify it so that it point to the correct msi but that didn't work.
any suggestion would be helpfull
i am using installshield version 11.5

Thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
In my own copy of InstallShield 11.5, in the "Setup Launcher" dialog of the Release Wizard, I see a drop down box offering different MSI Engine Versions (including v2.0, v3.0 and v3.1) which become visible when the "Create installation launcher (Setup.exe) tickbox is checked.

Are you saying that you don't see all of these options in your own copy of InstallShield ?

If so, I believe there were some issues around Windows Installer v3.1 integration in InstallShield 11.5 which are documented in this thread -- it may mean you need to obtain a hotfix for InstallShield to get this to work.

Regards,


Spartacus
Answered 09/06/2006 by: spartacus
Black Belt

Please log in to comment
0
i have see 3.1 if i am in a basic msi and i use the release wizard, but i don't see that 3.1 if i create a transform and then edit the transform
I am installing the hotfixes now so i will let you know what happen
Thanks
Answered 09/06/2006 by: linstead
Blue Belt

Please log in to comment
0
If you are able to see the v3.1 option when editing the base MSI, then it sounds like you didn't need the hotfix after all.

I don't think it is possible to use the Release Wizard when editing just the transform.

Instead, start the InstallShield Editor, click File .. Open .. browse to the vendor's MSI - making sure you select Wizard instead of Auto in the Open As box. This will allow you to "convert" the MSI to an InstallShield project (ISM) when prompted.

Once you have an ISM, you will be able to create a Release for the package using the Release Wizard, make sure you specify that you wish to use a Setup Launcher with the version 3.1 MSI engine). Once built, this will create a setup.exe that will install Windows Installer 3.1 first.

Now for the transform :

In order to use the transform (you have already created separately), the following installation command line should work :

setup.exe /v"TRANSFORMS=name_of_your_transform.mst"

Regards,

Spartacus
Answered 09/06/2006 by: spartacus
Black Belt

Please log in to comment
0
Thanks try that but i got too much error so i will just snap it

Thanks for all your help
Answered 09/06/2006 by: linstead
Blue Belt

Please log in to comment
1
This is a bad way of going about things anyway. Windows Installer 3.1 is a Windows patch. Including it in a setup is a bad idea for many reasons..
1) You should avoid setup's whenever possible
2) You can't uninstall it after
3) Some of your machines will have different patch levels depending on if they got this application
4) Requires a reboot.

Deploy the patch seperately to all machines ahead of time or you'll run into this issue everytime you have an app that requires 3.1.
Answered 09/06/2006 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity