Replacing a file in an MSI
I have an MSI admin install and I need to replace an file in it with a newer version. I don't have a compressed copy of the MSI. How do I go about replacing the file, including any requirements to update version details or package code in the MSI, baring mind that I need this package to repair correctly for existing installations too.
0 Comments
[ + ] Show comments
Answers (6)
Answer Summary:
Please log in to answer
Posted by:
pjgeutjens
12 years ago
I don't think you need the WSI step if it's an AIP you're working off. Just replace the file in the folder structure and change the pertinent entries in the File table.
You might even get away with a Small Upgrade in this case (only change Package Code). Just run through the checklist here: http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/MajorMinorSmall.htm
You might even get away with a Small Upgrade in this case (only change Package Code). Just run through the checklist here: http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/MajorMinorSmall.htm
Comments:
-
Yep...i missed this point on Small Upgrade. Ty for checking on me :) - akki 12 years ago
Posted by:
praveen.yeruva
12 years ago
Create a transform file . Delete the file to be replaced . and the add the file new file and save the file . Apply the transform to the base MSI .
Thanks .
Yeruva
Thanks .
Yeruva
Posted by:
bernhard riehemann
12 years ago
The first rule of a packager are:
1. Never touch a ventor MSI !!!
Create a MST, that is verry simple and the best way to create no errors or problems
1. Never touch a ventor MSI !!!
Create a MST, that is verry simple and the best way to create no errors or problems
Posted by:
akki
12 years ago
1. Convert the MSI into WSI
2. Delete the file that needs to be replaced.
3. Keep the newer version file at that location and than import it to your WSI.
4. Spin the package code and product code, taking into care not changing the upgrade
code.
5. Accordingly make changes to Upgrade table.
And you are good to go. :)
2. Delete the file that needs to be replaced.
3. Keep the newer version file at that location and than import it to your WSI.
4. Spin the package code and product code, taking into care not changing the upgrade
code.
5. Accordingly make changes to Upgrade table.
And you are good to go. :)
Comments:
-
Can I confirm why it's necessary to convert it to a WSI? Is this just best practice? - bos302 12 years ago
-
Yes it is considered as best practice but i agree with @pjgeutjens on just changing PackageCode. - akki 12 years ago
-
How about creating a transform . - praveen.yeruva 12 years ago
-
First rule of MSI packaging is to never repackage a vendor's MSI. You void all support and will have problems with future upgrades.
If this is an "in house" MSI, then modify it however you feel is right, but you could proboably ask the developer to make the change for you and give you an updated MSI. If this is a vendor's MSI, an MST is the best and safest course of action. - jmaclaurin 12 years ago-
@Praveen: Yes bro thats how it should be done. - akki 12 years ago
-
@Praveen: Yes bro thats how it should be done. - akki 12 years ago
-
@akki .. I want to tell you it should be done by creating a transform rather than converting MSI to WSI and then editing it .. anyways you corrected it .
Thanks. - praveen.yeruva 12 years ago
-
@jmaclaurin: You are absolutely correct brother, I dont know how could it possibly escape from my mind. Ty for correcting me. :) - akki 12 years ago
Posted by:
Bankeralle
12 years ago
The easiest way is just to replace the file in the folder structure.
Open the msi in for Wise. Change the version number for example to 1.0.0 to 1.0.1
Check the the Wiseversioninfo table. Delete the file you have replaced. Recompile
Open the msi in for Wise. Change the version number for example to 1.0.0 to 1.0.1
Check the the Wiseversioninfo table. Delete the file you have replaced. Recompile
