Repair bring backs the file I deleted using RemoveFile table in a patch?
Hi,
I've been trying to delete a file through a patch using MSI's RemoveFile table. The issue I'm facing is that as soon as I run repair the files comes back.
Now, this appears logical since InstallFiles action comes after RemoveFiles action. So the file is removed when patch is applied. But as soon as user does a repair which in turn causes a REINSTALL=ALL, the InstallFiles action installs the file back. I don't want the file to come back at patch or repair.
Is there a way I can achieve this without a custom action? I'm sure there must be a way to achieve this in Windows installer as it seems a very common scenario.
I've been trying to delete a file through a patch using MSI's RemoveFile table. The issue I'm facing is that as soon as I run repair the files comes back.
Now, this appears logical since InstallFiles action comes after RemoveFiles action. So the file is removed when patch is applied. But as soon as user does a repair which in turn causes a REINSTALL=ALL, the InstallFiles action installs the file back. I don't want the file to come back at patch or repair.
Is there a way I can achieve this without a custom action? I'm sure there must be a way to achieve this in Windows installer as it seems a very common scenario.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
naveen.packager
13 years ago
From original msi,delete the files from msi which you need to delete and create it as a 2nd msi. Then create a patch using these two msi's and then install the patch.
Hope it will work.
Hope it will work.
Posted by:
anonymous_9363
13 years ago
Yup, that's the correct way to create a patch. What you did in the first instance would normally be in a transform.
Please note that this forum is designed for posts relating to errors returned by the Windows Installer engine (see the link 'MSI Errors' for examples). You ought to have posted in the 'Package Development' forum. A moderator may move the thread.
Please note that this forum is designed for posts relating to errors returned by the Windows Installer engine (see the link 'MSI Errors' for examples). You ought to have posted in the 'Package Development' forum. A moderator may move the thread.
Posted by:
deployX
13 years ago
Thanks for responding. But while creating the new MSI can we modify the primary key in File table? Following link suggests that we should not modify primary key in File Table when creating a patch.
http://www.advancedinstaller.com/user-guide/patches.html
Oh! and I must also mention that I'm creating a MSP patch for a minor upgrade.
http://www.advancedinstaller.com/user-guide/patches.html
Oh! and I must also mention that I'm creating a MSP patch for a minor upgrade.
Posted by:
anonymous_9363
13 years ago
First things first...
You need to understand the difference between patching and upgrading. They are NOT the same thing. Get yourself off to MSDN and do some reading.
You need to understand the difference between patching and upgrading. They are NOT the same thing. Get yourself off to MSDN and do some reading.
Posted by:
deployX
13 years ago
Hi VBScab,
I know the difference between patching and upgrading and I'm trying to create a msp patch only to update my application.
But it seems that if I want to remove a installed file then I must delete it from File table but deleting it from File table creates sequencing issue when creating a msp.
I think I'll post to a wider audience under package development as suggested by you.
I know the difference between patching and upgrading and I'm trying to create a msp patch only to update my application.
But it seems that if I want to remove a installed file then I must delete it from File table but deleting it from File table creates sequencing issue when creating a msp.
I think I'll post to a wider audience under package development as suggested by you.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.