locked
Override or prevent an custom action in a upgrade in old version RRS feed

Answers

All replies

  • Hi Michael ZH,

    According to this blog http://blogs.msdn.com/b/astebner/archive/2007/05/31/3012427.aspx

    The writer "What I ended up doing was adding a condition of (NOT UPGRADINGPRODUCTCODE) in the InstallExecuteSequence table for each of the custom actions that I wanted to prevent from running during the major upgrade.  This allowed my major upgrade to work as expected and prevented the uninstall of the older version from breaking the newer version.  It also allowed a standard uninstall of the MSI to correctly execute these custom actions."

    I don't know what you mean by "has been released", but I think if it is released, it is already installed on target machine and this is the same with the condition that an old version has already been installed.

    By the way, I also saw one thread http://community.flexerasoftware.com/archive/index.php?t-184105.html which seems related to this case. They all directed us to MSI upgrade which is suit for you case.

    Regards,



    Barry Wang
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Thursday, May 1, 2014 8:02 AM
  • If you are referring to this problem, the solution is also here:

    http://support.microsoft.com/kb/906766/en-us


    Phil Wilson

    • Marked as answer by Barry Wang Thursday, May 8, 2014 8:59 AM
    Thursday, May 1, 2014 5:09 PM