Click here to Skip to main content
15,891,431 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hi All,

Using Installshieldx, we create a softphone application setup(install.exe) and its update patch setup(update.msp/single.exe) - for updating the installed older versions to the current version). The codebase of the application includes VB6.0 and C#.net projects. Apart from other required things, setup includes the following mergemodules - MFC,ATL,CRT,MFCLOC,OPENMP of version - 8.0.50727.762

Till now there is no problem as the version of merge modules is not changed.That is -
1. when we install the app setup(install.exe), the merge module dll's are getting created in the "C:\WINDOWS\WinSxS" path.
2. Otherwise, even if use the "update.msp/single.exe" upon installed older versions, there is no problem as the merge module dll's are already existing in the PC and patch is installed successfully and working fine.

Now, the application setup is required to integrate the updated version merge modules i.e 8.0.50727.4053 for the setup creation using the installshieldx.This is successful and the entire package with "install.exe" and "update.msp/single.exe" got created.

Since there is an update in the merge module version, we face a problem with the update.msp/single.exe. This can be explained as follows:
1. when we install the application using "install.exe", the latest version merge modules are getting created in the "winsxs" folder(previous version merge modules are also present here).
2. otherwise, if we use "update.msp/single.exe" of this build upon installed older/previous versions, the patch is installed successfully, but the updated version merge modules are not getting created in the "winsxs" folder, due to which the working of the patch fails.

Apart from the merge modules, "vs 2005 redistributable package" also installs the same dll's in the "winsxs" path. But we need these dll's to be installed along with
"update.msp/single.exe", for the proper working of the update patch.

We checked all the settings/configurations need to be done in the "installshieldx" for the creation of the "update.msp/single.exe", but still ending with this problem.

So, if anything that we are missing to do/any ideas/any suggestions/solution are greatly accepted and it would be very helpful to us.

Thanks in advance.
Posted

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900