Qt Forum
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Unsolved Version number doesn't change after upgrade in "Programs and features" Windows

    Installation and Deployment
    4
    8
    1634
    Loading More Posts
    • 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.
    • J
      Jero last edited by

      I deployed the version 1.0.0 of my application using QT Installer Framework 2.0.3
      In Windows the version number appears correctly in "Computer > Programs > Programs and features".

      Now I want to deploy the new version 1.1.0. I changed the version number in all the corresponding files, compiled and created a new installer. When I try to update to this new version the Installer recognises properly the new version (1.1.0 ) but after the installation the version remains the same (1.0.0) in "Computer > Programs > Programs and features".

      Any idea?

      1 Reply Last reply Reply Quote 0
      • hskoglund
        hskoglund last edited by

        HI in Windows there are 2 types of versions: a file version and a product version. maybe only of them got updated them from 1.0.0 to 1.1.0 when you changed to 1.1.0. And perhaps Computer > Programs > Programs is looking at one of them, and the installer at the other...

        1 Reply Last reply Reply Quote 1
        • Paul Colby
          Paul Colby last edited by

          in Windows there are 2 types of versions: a file version and a product version.

          Yep, and both of those can be embedded as resources. But the installed application version (as shown in the Programs and Features windows) uses neither of those. It uses registry keys that the installer should be setting - ie the DisplayVersion subkey under a key like Software\Microsoft\Windows\CurrentVersion\Uninstall\<appname>, within the relevant hive (usually HKLM or HKCU).

          I'm not sure how the Qt Installer Framework handles this though. Either it extracts the version automagically from your exe, or its a separate configuration property you set?

          (sorry I can't be more helpful... I haven't used QIF yet).

          Cheers.

          1 Reply Last reply Reply Quote 0
          • Paul Colby
            Paul Colby last edited by

            or its a separate configuration property you set?

            Are you setting the <Version> element as shown in http://doc.qt.io/qtinstallerframework/ifw-globalconfig.html ?

            Cheers.

            1 Reply Last reply Reply Quote 0
            • J
              Jero last edited by

              Thank you very much for the answers.
              I changed the version number in all the suggested places so I think probably the approach is to include an entry in the registry under the "Uninstall" key. I will try and let you know the outcome. Thx!

              1 Reply Last reply Reply Quote 0
              • J
                Jero last edited by

                Indeed the the global config files creates an entry in the registry, including an "uninstall" key and the DisplayName and DisplayVersion information, the problem is that this information is not changed when updating the application through an online repository as QT Installer Framework allows. I think this is a bug. Thank you for the help.

                1 Reply Last reply Reply Quote 0
                • J
                  Jero last edited by

                  I forgot to add that if I install from scratch both versions, then the version is properly shown in "Programs and features" 1.0.0 in first case, 1.1.0 in second case, the issue appears only in the update transition, when I have already the 1.0.0 installed.

                  1 Reply Last reply Reply Quote 0
                  • R
                    R Kh last edited by

                    For traceability: the bug report is QTIFW-900. No joy there either, unfortunately.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post