locked
Setup project problem: new msi of new version doesnot update project content files RRS feed

  • Question

  • Hi,

    I have a setup project for my application and it works fine. and now I am trying to do a update for the application. I did following in the setup project properties:
     - changed the version in the setup project, 
     - said "Yes" to change ProductCode. 
     - set "RemovePreviousVersions" to true

    And then I rebuilt the setup project, ran new msi and answer all questions (didn't ask me whether want to upgrade though ??) So far it seems fine, but when I check for installed files, I could see the documentation files and other addition files is updated, but the main executable and dlls remains as old version.

    What addition did I need to do?
    Please help, thank you.

    Maggie
    • Changed type BonnieBMVP Saturday, December 5, 2020 11:23 PM Question
    Tuesday, April 7, 2009 9:35 PM

All replies

  • You need to set UpgradeCode property of setup project to some guid. You will find this in the properties of the project if you work with Visual Studio 2005 and newer. You will need orca if you use Visual Studio 2003.
    MCDBA, MCSD, MCITP DD&DA http://sharpsource.blogspot.com/
    Tuesday, April 7, 2009 9:45 PM
  • I am using VS2008. 

    I didn't change UpgradeCode property when I did rebuild on the setup project

    I just check my backup, and UpgradeCode are same in both version
    Tuesday, April 7, 2009 9:57 PM
  • Probably stupid, but do I need to raise the version of my project assembly in the same time I change version in setup project? If it is the case, what's difference of project assembly version and setup project version? and how do they affect in upgrade installation process?

    Please help, thanks.
    Thursday, April 9, 2009 2:43 PM
  • You don't have to do that. If you set all the properties required and don't change them you will be fine. Those are:
    Author (maybe you can change it without any issues)
    Manufacturer
    Product Name
    RemovePreviousVersions=True
    ProductCode
    UpgradeCode

    I also set:
    InstallAllUsers=True
    DetectNewerInstalledVersion=True
    Title
    Version


    MCDBA, MCSD, MCITP DD&DA http://sharpsource.blogspot.com/
    Thursday, April 9, 2009 4:02 PM
  • Thank you, Boban for your reply.
    Unfortunately, I still cannot get the upgrade works.

    this is my settings

    Author                                   My Department
    Description
    DetectNewerInstalledVersion   True
    InstallAllUsers                        True
    Keywords
    Localization                            English
    Manufacturer                          My Company
    ManufacturerUrl
    PostBuildEvent                       post.bat
    PreBuildEvent
    ProductCode                          {11111111111111111111}
    ProductName                         MyApp
    RemovePreviousVersion         False
    RunPostBuildEvent                 On successful build
    Search Path
    Subject
    SupportPhone
    SupportUrl
    TargetPlatform                      x86
    Title                                     MyAppSetup
    UpgradeCode                       {222222222222222222222}
    Version                                1.0.0

    and what I did is change Version 1.0.0 to 1.3.0, and said "Yes" to change "ProductCode" to {33333333333333333} , and then rebuilt setup project.

    Did I miss anything?
    Please help. Thanks.

    Maggie

    Thursday, April 9, 2009 6:31 PM
  • After doing some tests, I finally get the answer. Assembly versions  and file versions of projects that were included in setup project "Project Output" must be upgraded in the same time as the setup project changing version. Or these files won't be upgraded when doing upgrading setup.

    Other people doesn't have same problem as me, I guess they using some kind of source control, such that file verison and assembly version were updated automatically everytime they were built. I didn't use any source control (I am not working in a professional software company), and this is hard to find it out. Thanks Microsoft!!
    Wednesday, April 29, 2009 4:13 PM
  • Updating version number worked for me. Upgrading using installer worked for me.

    Friday, December 4, 2020 2:02 PM