adding external files to MST .key .dll
Hi, I have been tasked with creating a MST which includes an included .ini file change an external .key file, and an unrelated MS office web component dll (MSOWC.dll). I have or so I believe created this successfully, a cab file contains the required files, on installation, only the file included within the original MSI (although with the updated information) exists on the machine, the other 2 files are not installed. Am I doing something abundently wrong?
First off the files are located in (sharepoint)\(appname)\(correct directory tree) in the source,
they are pointed to as \program files\eqm\bin\ eqm.key + qmss.ini
the MSOWC.dll is pointed to program files\microsoft office\office11
MSOWC.dll is in it's own component, set as a key file.
Do I need to do anything for this to work? I am thoroughly confused.
First off the files are located in (sharepoint)\(appname)\(correct directory tree) in the source,
they are pointed to as \program files\eqm\bin\ eqm.key + qmss.ini
the MSOWC.dll is pointed to program files\microsoft office\office11
MSOWC.dll is in it's own component, set as a key file.
Do I need to do anything for this to work? I am thoroughly confused.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
nheim
17 years ago
Hi,
are you logging the install? What does the logfile say about this files?
Have you put the cabfile correctly in to the media table?
Regards, Nick
are you logging the install? What does the logfile say about this files?
Have you put the cabfile correctly in to the media table?
Regards, Nick
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
