We have created an install package and are now testing applying a patch to the programme.
However...
After installing the patch, when we run the uninstaller, only the files installed by the patch areuninstalled, everythning else installed by the original installer is left over.
Has anyone had any experience with this and managed to fix it?
Thanks
Patches
This is not a known issue with patches - when uninstalling, all files are removed.
Using patches can be tricky at times. Please look for Patching in the InstallAware help index, and read the topic titled Patching. Make sure you are following the patch requirements described in that topic, under the Patch Requirements heading.
Using patches can be tricky at times. Please look for Patching in the InstallAware help index, and read the topic titled Patching. Make sure you are following the patch requirements described in that topic, under the Patch Requirements heading.
Hi, Sorry that doesn't really help, I've checked in the help index a few times, but can't seem to find an answer to the problem. The upgrade & product codes are identical and the revision codes are different. We've implemented the main installer to copy the install files to the local hard drive to save having to put the cd in each time a user wishes to apply a patch. the patch then references this msi which is identical to the original installer.
Any further ideas?
Any further ideas?
Main Application build process:
Main build has been created using ‘Compressed Web-Based Exe’
Patch build process:
A new project has been created, replacing on dll file in the main build target folder as well as adding a registry key.
The previously build setup.exe has then been linked as patch reference.
The same product code has been specified for the patch project as well as for the main application. The patch project has been set to upgrade products with this product code. The revision code is different to the main setup.
The patch has then been build with the ‘Build Patch’ option.
With the outcome that only the changes made by the patch were uninstalled.
Now, there’s one thing to clarify:
In the application setup project, should the ‘Upgrades products with Product Code’ field be the same as the Product Code or different? In any case, it didn’t make a difference in both scenarios.
Version of installaware is:
Installaware 2005 - sp1.pasion_update1_rtm.050909
The procedure to reference the files is as follows:
We create a sub build which is identical to the main build without the reference to msde, mdac and windows installer. This build is then placed into the target root of the main build so when the main build is compiled, the sub build is incorporated into it. The msi in the data folder is referenced by the patch
Main build has been created using ‘Compressed Web-Based Exe’
Patch build process:
A new project has been created, replacing on dll file in the main build target folder as well as adding a registry key.
The previously build setup.exe has then been linked as patch reference.
The same product code has been specified for the patch project as well as for the main application. The patch project has been set to upgrade products with this product code. The revision code is different to the main setup.
The patch has then been build with the ‘Build Patch’ option.
With the outcome that only the changes made by the patch were uninstalled.
Now, there’s one thing to clarify:
In the application setup project, should the ‘Upgrades products with Product Code’ field be the same as the Product Code or different? In any case, it didn’t make a difference in both scenarios.
Version of installaware is:
Installaware 2005 - sp1.pasion_update1_rtm.050909
The procedure to reference the files is as follows:
We create a sub build which is identical to the main build without the reference to msde, mdac and windows installer. This build is then placed into the target root of the main build so when the main build is compiled, the sub build is incorporated into it. The msi in the data folder is referenced by the patch
Since you are creating the main build using the compressed web based exe option, patch source resolution should be automatic (as described in the help file). Was this not the case?
I have a hunch the sub build you are creating and referencing is most likely causing the issue. Can you leave the sub build out, and don't explicitly reference anything while running the patch, letting it resolve its source automatically (as should happen since your main build is a web build)?
Why did you start creating the sub build and referencing that?
I have a hunch the sub build you are creating and referencing is most likely causing the issue. Can you leave the sub build out, and don't explicitly reference anything while running the patch, letting it resolve its source automatically (as should happen since your main build is a web build)?
Why did you start creating the sub build and referencing that?
Who is online
Users browsing this forum: Baidu [Spider] and 50 guests
