Upgrade issue for a application
I am doing an application in which I just need to replace a file with new one. But my requirement is that the previous version should uninstall then my package with new file should install.
I have created a mst which just contains the new file and changed product name and product code.
I have given entries in upgrade table as well Like upgrade code of previous application, max version, min version, attributes, Action property. I have given an entry for ACTION Property in property table as well.
Any help???
Regards,
Kaushal
I have created a mst which just contains the new file and changed product name and product code.
I have given entries in upgrade table as well Like upgrade code of previous application, max version, min version, attributes, Action property. I have given an entry for ACTION Property in property table as well.
Any help???
Regards,
Kaushal
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
slay_u
14 years ago
exactly, you need to be clear with your query here...
If I have got you right, are you trying to do a major upgrade here ? If yes did you try the REINSTALLMODE and REINSTALL properties ?
If I have got you right, are you trying to do a major upgrade here ? If yes did you try the REINSTALLMODE and REINSTALL properties ?
Posted by:
anonymous_9363
14 years ago
You can't use an MST to perform any kind of upgrade. Search MSDN for details about how to author upgrade packages.
Posted by:
kaushal019
14 years ago
Actually i am creating a mst for vendor msi. I only need to replace a file in this vendor msi and change the product name as given standards only. I do not have to do any major upgrade. My requirement is that when i install my mst with base msi, the previous application should uninstall and my new application(base msi + mst) should install new file along with changed product name.
I have put an entry in upgrade table as well in my mst. Like upgrade code of base msi along with min version 1.0 and maximum version 2.0 with attibutes (517) and action property. I have put entry for action property in Securecustomproperties as well.
Also in my new application(base msi + mst), I have changed product code as well for the upgrade to take place. Please note that my base msi version is 2.0. And the new package will also have version 2.0. i have put "RemoveExistingzProducts" action in between "InstallValidate" and "InstallInitialise" .
Any Help Folks??
I have put an entry in upgrade table as well in my mst. Like upgrade code of base msi along with min version 1.0 and maximum version 2.0 with attibutes (517) and action property. I have put entry for action property in Securecustomproperties as well.
Also in my new application(base msi + mst), I have changed product code as well for the upgrade to take place. Please note that my base msi version is 2.0. And the new package will also have version 2.0. i have put "RemoveExistingzProducts" action in between "InstallValidate" and "InstallInitialise" .
Any Help Folks??
Posted by:
anonymous_9363
14 years ago
You're confused. In one breath you're saying that you "only need to replace a file in this vendor msi". Then you say that you want to uninstall a previous version and install the new file. Why uninstall, if it's only one file?
If you simply want to use a different file in the MST than the one in the original MSI, you don't need to mess with the Upgrade table, ProductCode, etc, etc. You will obviously need to pay attention to version info (if the file contains it) or to date/time-stamps. I wouldn't describe that as best practise, however, especially given that this is a vendor MSI.
If you want to actually upgrade, i.e. effectively remove v1 and replace it with v2, then you CANNOT use a transform for that. As I said, READ the MSDN article about upgrades. Surely the vendor has an MSI/MSP for this upgrade?
If you simply want to use a different file in the MST than the one in the original MSI, you don't need to mess with the Upgrade table, ProductCode, etc, etc. You will obviously need to pay attention to version info (if the file contains it) or to date/time-stamps. I wouldn't describe that as best practise, however, especially given that this is a vendor MSI.
If you want to actually upgrade, i.e. effectively remove v1 and replace it with v2, then you CANNOT use a transform for that. As I said, READ the MSDN article about upgrades. Surely the vendor has an MSI/MSP for this upgrade?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.