Hello,
during the last days i learned much about the windows installer framework, but even when i thought, i got a better understanding of it, new problems and questions appearing.
Here is the newest:
During our build process i have produced severel mst-files, which will be included with the main .msi-file to self-extracting setup.exe.
I know how to apply the mst-files by using the command line and msidb.exe from the sdk, but on the target machine these msidb.exe is surely not present. I guess, i had to use the msiquery-api and the function msidatabaseimport, but the documentation of that function is not very clear.
In my opinion it has to work like this:
Getting a msi-handle and the relating mst-file and then, by using the msidatabaseexport-function export, the transformed msi-file, which will be started with the specified localization.
Is that correct?
I'm not familiar with the windows-api, that's why i ask.
Thanks for a little help!
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Applying a .mst with the MSI API
Started by
mfw
, Sep 23 2005 08:39
1 reply to this topic