Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. .NET (Core and Framework)
  4. VERSIONING

VERSIONING

Scheduled Pinned Locked Moved .NET (Core and Framework)
tutorialworkspace
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    balakpn
    wrote on last edited by
    #1

    hi i want to rebuild my setup file with new changes on my code and have to give it to endusers. the thing i want is i don want them to uninstall the older one i want to upgrade the installed one.how to do that

    with regards Balagurunathan.B

    S 1 Reply Last reply
    0
    • B balakpn

      hi i want to rebuild my setup file with new changes on my code and have to give it to endusers. the thing i want is i don want them to uninstall the older one i want to upgrade the installed one.how to do that

      with regards Balagurunathan.B

      S Offline
      S Offline
      Scott Dorman
      wrote on last edited by
      #2

      You need to make sure that the version number for all of your binaries is higher than the previous version number. If you are using an MSI installer, you also need to change the upgrade code and the product version (I think that's the field name, but I'm not 100% sure...either way, it should be the only version number in the setup project) so that the Windows Installer service recognizes that this is a different version. Keep in mind that MSI only looks at the first 3 portions of the product version when determining if the installer is newer or not.

      ----------------------------- In just two days, tomorrow will be yesterday. http://geekswithblogs.net/sdorman

      M 1 Reply Last reply
      0
      • S Scott Dorman

        You need to make sure that the version number for all of your binaries is higher than the previous version number. If you are using an MSI installer, you also need to change the upgrade code and the product version (I think that's the field name, but I'm not 100% sure...either way, it should be the only version number in the setup project) so that the Windows Installer service recognizes that this is a different version. Keep in mind that MSI only looks at the first 3 portions of the product version when determining if the installer is newer or not.

        ----------------------------- In just two days, tomorrow will be yesterday. http://geekswithblogs.net/sdorman

        M Offline
        M Offline
        Mark Churchill
        wrote on last edited by
        #3

        Change the version number in the installer properties and VS will remind you to change the product code. Then you might want to flick on the "Remove previous versions" property, to make the upgrade less painful.

        Mark Churchill Director Dunn & Churchill

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups