Can't add merge module to package w/WPS 3.2
I am trying to add a merge module to an existing .msi using Wise Package Studio 3.2.
I can add the module, but it does not "stick" after I complile/save. In other words, the merge module is not there once I re-open the .msi for editing.
This is happening regardless of the .msi or the .msm I use.
Has anyone run into this?
Thanks in advance,
Craig --<>.
I can add the module, but it does not "stick" after I complile/save. In other words, the merge module is not there once I re-open the .msi for editing.
This is happening regardless of the .msi or the .msm I use.
Has anyone run into this?
Thanks in advance,
Craig --<>.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
craig16229
16 years ago
It's been three years since I posted this, but I thought I would circle back around since I just now figured it out:
I should have figured it out sooner since I have been using WPS since version 3 and I am currently using version 7 sp2.
Adding the merge modules WITH the source files still present was the solution. I still had my vmWare machine in the state it was in from the original raw/unedited compile of my package. With the source files available and also by de-selecting "don't update or re-compress files when saving" under "Installation Expert / Product Details", my .msi re-compiled fully. When I re-opened my .msi, the merge modules were finally there.
I guess I should have been able to figure this out sooner, but I feel this is an important requirement of adding merge modules that should be added to the help file, and/or program in a error message if you are trying to add an .msm to a compilation when the source files are not present. In my case, I was editing the .msi after it was extracted to my administrative installation point on the deployment server. Obviously, the original source files are not present at that point.
Craig
I should have figured it out sooner since I have been using WPS since version 3 and I am currently using version 7 sp2.
Adding the merge modules WITH the source files still present was the solution. I still had my vmWare machine in the state it was in from the original raw/unedited compile of my package. With the source files available and also by de-selecting "don't update or re-compress files when saving" under "Installation Expert / Product Details", my .msi re-compiled fully. When I re-opened my .msi, the merge modules were finally there.
I guess I should have been able to figure this out sooner, but I feel this is an important requirement of adding merge modules that should be added to the help file, and/or program in a error message if you are trying to add an .msm to a compilation when the source files are not present. In my case, I was editing the .msi after it was extracted to my administrative installation point on the deployment server. Obviously, the original source files are not present at that point.
Craig
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.