V
Viviana Vc
Hi all,
One way of building the release is having just a msi file without
anything else, no CABs, no setup.exe, no external files.
I know that the MSI file contains all the tables that reflect the
inteligence of that specific installer, but I wasn't sure that also the
application files can be packed into the MSI.
1) As everything in a MSI are tables which table contains the content of
those files? Or how are those files stored in the MSI?
2) As discussed in another thread the MSI files (without the CABs) are
cached in the WindowSystem\Installer folder. In this case, when there is
a MSI file containing everything packed in, is cached the whole MSI
meaning also the files that are part of the package?
3) Also in case I want to replace a file from a MSI package how could I
do that with Orca?
4) What kind of release version would system administrators preffer:
CD-ROM, Network compressed, uncompressed, etc?
Thx,
Viv
One way of building the release is having just a msi file without
anything else, no CABs, no setup.exe, no external files.
I know that the MSI file contains all the tables that reflect the
inteligence of that specific installer, but I wasn't sure that also the
application files can be packed into the MSI.
1) As everything in a MSI are tables which table contains the content of
those files? Or how are those files stored in the MSI?
2) As discussed in another thread the MSI files (without the CABs) are
cached in the WindowSystem\Installer folder. In this case, when there is
a MSI file containing everything packed in, is cached the whole MSI
meaning also the files that are part of the package?
3) Also in case I want to replace a file from a MSI package how could I
do that with Orca?
4) What kind of release version would system administrators preffer:
CD-ROM, Network compressed, uncompressed, etc?
Thx,
Viv