NetSeeker
12-30-2003, 03:38 PM
During the install process there are several files expanded to the %TempLaunchDir% folder.
Remarkable is the file irsetup.exe witch has a size of 712 KB
that must be compressed about 400 KB - round about the size an empty setup has. There is the whole setup functionality located in.
if this file would be smaller, the whole setup would be smaller. this file is located in the Data Folder with the name w32wiz.da2. This file is so big, because it contains the whole functionality of the SUF6 runtime.
There are several easy ways to size this file down:
They are all based on the determination witch functionality is needet at design time (From Actions)
1. The simple way:
Provide several irsetup.exe files with reduced functionality and include the "right" one. Dhe Build of the several alternatives can be done with your compiler makefile or IDE Project
2. the more complex way:
Seperate the functionality in DLL's and include only the DLL's that are needed. (Link to the DLL's in a dynamic way with LoadLibrary and GetProcAdress)
3. The Hard way:
Dynamically build irsetup.exe with exactly the functionality needet for a particular setup
Remarkable is the file irsetup.exe witch has a size of 712 KB
that must be compressed about 400 KB - round about the size an empty setup has. There is the whole setup functionality located in.
if this file would be smaller, the whole setup would be smaller. this file is located in the Data Folder with the name w32wiz.da2. This file is so big, because it contains the whole functionality of the SUF6 runtime.
There are several easy ways to size this file down:
They are all based on the determination witch functionality is needet at design time (From Actions)
1. The simple way:
Provide several irsetup.exe files with reduced functionality and include the "right" one. Dhe Build of the several alternatives can be done with your compiler makefile or IDE Project
2. the more complex way:
Seperate the functionality in DLL's and include only the DLL's that are needed. (Link to the DLL's in a dynamic way with LoadLibrary and GetProcAdress)
3. The Hard way:
Dynamically build irsetup.exe with exactly the functionality needet for a particular setup