/build/static/layout/Breadcrumb_cap_w.png

Issues with upgrading same versions of application

Hi, current application is a legacy application for which I am creating a MSI with new product code and upgrade code.Now the build where I have to test the app,contains the same version of app with different product code and upgrade code.Now when I am trying to upgrade it, it is not working.the older app is not getting uninstalled and the ARP contains both old and new app entry.
I have browsed the old MSI taking it from Installer folder(checked whether it is the right MSI) in the upgrade table of my app, kept the max version same as my app, min version null. In upgrade table, attribute is 517 and REP CA is placed after Install Validate.Also tried placing REP after APPsearch and checked.
Tried to keep upgrade code of both app the same.But upgrade not working in any case.
Is there any way out or manually I have to write a CA to uninstall it?
Please suggest

0 Comments   [ + ] Show comments

Answers (2)

Posted by: anonymous_9363 14 years ago
Red Belt
0
List your ProductCode and UpgradeCode, along with a tabular representation of your Upgrade table.

Also, are you sure you have the relevant ActionProperty included in the SecureCustomProperties list?
Posted by: sapto123 14 years ago
Senior Yellow Belt
0
Guys...I got it to work.Just removed the Language Code from the Upgrade table and the package worked.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ