Hello folks,

I am trying to uninstall a previous version of an application using the new version.

I tried with the below methods but didn't work.

1. Had the same upgrade code for both the versions. ---> didn't work
2. Witha diffrent upgrade code added a new row to upgrade table with old upgrade code and version and attributes=512 and RemoveExistingProducts as Action ---> Still didn't work.

Is there anything I am overlooking.

I did the same thing for so many applications they seemed to be working fime. But not this.
Note: this is a capture in both the versions.

Thanks,
Ram.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hello folks,
Got it working

I had to add the an value REMOVEEXISTINGPRODUCTS to the property SecureCustomProperties .

Thanks,
Ram.
Answered 12/21/2008 by: Ram
Senior Purple Belt

Please log in to comment
0
REMOVEEXISTINGPRODUCTS ORIGINAL:
Got it working

I had to add the an value REMOVEEXISTINGPRODUCTS to the property SecureCustomProperties .



Glad it worked, but I'd be cautious of naming a property REMOVEEXISTINGPRODUCTS , because RemoveExistingProducts is also the name of a standard action.
Answered 12/22/2008 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
In some cases you must move the action RemoveExistingVersion to be located just efter InstallValidate and before InstallInitialize, meaning sequence 1450.

/Göran
Answered 12/22/2008 by: fetgor
Senior Purple Belt

Please log in to comment
0
"Must"? Hmmm...I wouldn't go that far. MS guidelines state that it should be as near the end of the sequence as possible, in order to minimise unncessary file removals. That is to say, it's their contention that, if a file is to be replaced, overwriting it (by the InstallFiles action) is more efficient than removing it first (which RemoveExistingProducts might do) and then installing the later version anyway. So much depends on whether the files in question contain version information or or correctly date/time-stamped, of course.

Quoting an actual sequence number is fairly pointless, as each MSI will have completely different sequence numbers.
Answered 12/23/2008 by: VBScab
Red Belt

Please log in to comment
0
Thank you All,
Yes I do understand that it wasn't necessary to rempve if the version had minor changes but It is bit more than that. So had to uninstall the application and reinstall the new version..

Regards,
Ram.
Answered 12/23/2008 by: Ram
Senior Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity