Forcing Web Packages to be cached locally

[Gareth Owen]

Is it possible to force ALL of the Web modules to be cached during the installation?

I am trying to allow our users to easily modify their installations, e.g add additional components.

We need to ship the installation in a compressed form as we have limited space on the CD, and we do not want our users to have to manually uncompress the setup exe to add additional modules.

I tried using Web modules located in the same directory as the installation exe, and the initial installation works fine, but If you try and modify the installation, and select an item that was not in one of the web modules originally installed, the installer tries to get the web modules from the web, which do not exist as we had them located on the installation CD.

Is it possible to get all modules included in the installation cache, or do I have to place all of my files in a single web module.

[sinan]

Yes, you may do this. Extract all files directly to the setup engine folder during installation using the Extract 7Zip Archive command. The setup engine folder is found here:

C:\\Documents and Settings\\<user>\\Application Data\\<revision GUID>

You can get the path to the application data folder, of course, using Get Folder Location.