2 replies to this topic

[jonathan2002]

This follows on from my earlier topic "Reducing installation size". I found I could achieve this by adjusting the Release wizard so that the InstallScript engine would be downloaded, and that the files would all be compressed into 1 setup.exe.

This greatly cut the size of the installation. When I tried it out on a test machine, it seemed to go through a downloading stage on the "Ready to install" dialog at the beginning, after which the installation ran ok (the test machines do not have installengine installed, and so will not run a slimmed down version by itself).

Unfortunatuely, I haven't been able to reproduce the setup I had that achieved the downloading stage - I find since then that I always get errors "Instmsia.exe not found" when I run it. I know I can manually download this and run it from the web, but what I want is to set up my installation so that if it doesn't have the installengine, it automatically downloads it from the web.

I thought I had it set up to do that but seems I misunderstood. The problem arises because my test machines don't have installer on them. I want to be able to deploy to such machines without including the engine in my installation.

Exactly what URL should I put in the "InstallScript engine" screen of the Release wizard?

My installation is a basic MSI project with installscript. That is the most convenient way I have found to develop.

[Stefan Krueger]

Note that there are two different engines: the InstallScript  engine (iscript.msi), and the Windows Installer runtime (instmaia.exe and instmsiw.exe). In the release wizard, there are different panels where you can select whether to include or download these engines, and the URL.

[jonathan2002]

Thanks - I've now sorted out the trouble, and got both engines downloaded if necessary.