?? Include ISScript.msi in another msi ??

[bertilh]

Hi,

From now on, the only way that I found to include the IS Script engine into a setup is to create a setup.exe.

What if I do not want to create a setup.exe but an msi package?
Is it possible to include the IS Script engine? How? Nested installation...?

Note that the script engine must be installed before the main package that needs the script engine... (ISScript Custom Actions)

Any help would be greatly appreciated

Thanks

[AlaksSevugan]

If you are creating projects that include InstallScript, then I would recommend that you distribute the ISScript.MSi separately to all the client machines first.

Then when you create a MSi using installscript, you can deploy them to client machines since you know you have already primed the client machines with the installshield script engine.