Setup Project Not Removing Previous Version

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • zacks@construction-imaging.com
    #1

    Setup Project Not Removing Previous Version

    I have created numerous Setup projects with Visual Studio 2005. I have
    a current solution that is fairly complex with numerous projects. It
    contains two primary applications so there are two setup projects. The
    setup project for the first application works fine, it removes the
    previous version automatically just fine as long as I have incremented
    the Version property. But the more recent Setup project for the second
    application refuses to remove the previous version. All properties
    related to this feature are identical. DetectNewerInst allation is
    True. RemovePreviousV ersion is True. I increment the Version and it
    asks me if I want to update the ProductCode and I always answer Yes.
    Install the app, go to AddRemove programs and now there are two
    versions installed, both the previous one and the new one.

    I have done web searches on this and cannot find any solution. Does
    anyone have any ideas?

    Tags: None
    • Ignacio Machin \( .NET/ C# MVP \)
      #2
      Re: Setup Project Not Removing Previous Version

      Hi,

      <zacks@construc tion-imaging.comwrot e in message
      news:1188499937 .199361.106800@ q5g2000prf.goog legroups.com...
      >I have created numerous Setup projects with Visual Studio 2005. I have
      a current solution that is fairly complex with numerous projects. It
      contains two primary applications so there are two setup projects. The
      setup project for the first application works fine, it removes the
      previous version automatically just fine as long as I have incremented
      the Version property. But the more recent Setup project for the second
      application refuses to remove the previous version. All properties
      related to this feature are identical. DetectNewerInst allation is
      True. RemovePreviousV ersion is True. I increment the Version and it
      asks me if I want to update the ProductCode and I always answer Yes.
      Install the app, go to AddRemove programs and now there are two
      versions installed, both the previous one and the new one.
      >
      I have done web searches on this and cannot find any solution. Does
      anyone have any ideas?
      >
      Maybe they have different product codes or upgrade codes. That might prevent
      the new version to find the old one.


        Comment

        • zacks@construction-imaging.com
          #3
          Re: Setup Project Not Removing Previous Version

          On Aug 30, 3:32 pm, "Ignacio Machin \( .NET/ C# MVP \)" <machin TA
          laceupsolutions .comwrote:
          Hi,
          >
          <za...@construc tion-imaging.comwrot e in message
          >
          news:1188499937 .199361.106800@ q5g2000prf.goog legroups.com...
          >
          >
          >
          >
          >
          I have created numerous Setup projects with Visual Studio 2005. I have
          a current solution that is fairly complex with numerous projects. It
          contains two primary applications so there are two setup projects. The
          setup project for the first application works fine, it removes the
          previous version automatically just fine as long as I have incremented
          the Version property. But the more recent Setup project for the second
          application refuses to remove the previous version. All properties
          related to this feature are identical. DetectNewerInst allation is
          True. RemovePreviousV ersion is True. I increment the Version and it
          asks me if I want to update the ProductCode and I always answer Yes.
          Install the app, go to AddRemove programs and now there are two
          versions installed, both the previous one and the new one.
          >
          I have done web searches on this and cannot find any solution. Does
          anyone have any ideas?
          >
          Maybe they have different product codes or upgrade codes. That might prevent
          the new version to find the old one.
          I have never messed with the Upgade Code. The Product Code gets reset
          every time I change the Version.

            Comment

            Previous template Next
            Working...