First, thanks for taking the time to explain all of this, as I said this is all new to me.
I'm using VS 2008, and for whatever reason it didn't delete the file as part of the update. I've also got it set to not do so using Wix by not specifying a GUID for that component (a user can put a lot of work into updating this file, and I don't want them to lose it if they don't' want to. I'm hoping to make this an option at some point, but reading about what it takes to get in the middle of the uninstall process pushes this way down the list). What I'm trying to do is just upgrade the executables, but not include the data files or modify the registry keys or shortcuts that I create in an install, but update the version number that Add/Remove knows about and just have the one entry in Add/Remove. The major upgrade in setup seems to leave the shortcuts and registry data and data files alone, but does update the version number in Add/Remove and just keeps the one entry (exactly what I want). Is there a way to do this in Wix? I even tried setting the UpgradeCode the same in the Wix install and the .NET setup upgrade, but no joy. When I install, change version#, update, change version #, update again, then the two updates seem to work the way I want, the second one just updates the version # in Add/Remove without adding another entry. I know I'm missing something basic here, but I don't know what. Sigh -----Original Message----- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Tuesday, May 18, 2010 3:41 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Upgrade installation What you're describing is a major upgrade. You didn't mention this, but Visual Studio setup projects typically have RemovePreviousVersions set true, that would cause an upgrade where the old version of the product would be uninstalled. That's what incrementing ProductVersion, changing the ProductCode and keeping UpgradeCode the same results in. Yes, that would be an upgrade, and it removes the older product (which is why you see only one entry in Add/Remove Programs). But it is a Windows Installer major upgrade that uninstalls the old product and installs the new one, so it should have removed that large file that you want to keep. If it did not remove it then that was a happy accident because that's not the way it works. If your setup project was built with VS 2005 or prior, RemovePreviousVersions (RemoveExistingProducts in MSI-speak) runs at the start of the upgrade, removing all the old files and the product, and then installing the new one. It is an upgrade in the sense of uninstall of the old then install the new, not in the sense of "I'm adding something to this already installed product". So I can well believe you got a major upgrade to work using RemovePreviousVersions, that's not the issue. The issue is that you can't keep that large file (from the first install) on the system if you do a major upgrade and do not include it in the second upgrade install. Phil Wilson 949-639-1680 -----Original Message----- From: Wix Mailing List [mailto:w...@danhinsley.com] Sent: Tuesday, May 18, 2010 1:39 PM To: Wilson, Phil Subject: RE: [WiX-users] Upgrade installation Using the .NET Visual Studio Setup Project, I set the UpgradeCode of both the Install setup project and the Update setup project to be the same. I build and run Install. I look in Add/Remove and I have one entry with the version number I used to build Install. Then I change the version # and the ProductCode in the Update project and build and run it. I end up with just one entry in Add/Remove, with the newer version # (if I don't change the version # and productcode, then I go into maintenance mode). So I am changing the product code, the Upgrade code is what stays the same. So I know this can be done (as the .NET setup project does it). But there must be something I need to do with Wix to end up with the same result. Make sense? -----Original Message----- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Tuesday, May 18, 2010 12:55 PM To: w...@danhinsley.com; General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] Upgrade installation I'll assume a .NET setup is a Visual Studio Setup Project, but anyway there's something missing in your description. You may have to be more precise about what you did. If you install an MSI file with a ProductCode, then that product guid is on the system, that's the definition of a product. If you now rebuild your MSI file with different content, and the ProductCode is the same (and you don't install it with a special command line) then it will go into maintenance mode when you try to install it. In Visual Studio setups that's a Repair/Remove choice. If you choose Repair then it does not use your new MSI file. It effectively says, oh, this ProductCode is already installed, and it uses the existing installed (cached) MSI file to do a repair. There'll be one entry still in Add/Remove Programs but there will be no new content from your new MSI file on the system. The other possibility could be that you (inadvertently?) used RemovePreviousVersions in your VS setup project, but that doesn't make sense if your ProductCode was the same in both your MSI files. That's the underlying issue - there is no such thing as an upgrade install when the ProductCode stays the same between two builds of an MSI file (unless you install the second one as a patch by reinstalling the entire new MSI file with a command line specifying REINSTALL and REINSTALLMODE). Them's the MSI rules no matter what tool you use to build your MSI file. So it comes down to exactly what you did and saw in your "upgrade". Phil Wilson -----Original Message----- From: Wix Mailing List [mailto:w...@danhinsley.com] Sent: Tuesday, May 18, 2010 12:04 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Upgrade installation If you have two separate MSI files then you'll have two entries in Add/Remove Programs. There's no magic merge that makes them become one product. >> But I did the same type of thing using the .NET setup (which produces MSI files) and it did as I expected. The upgrade recognized that it was the same product as the initial install, and I only ended up with the one entry in Add/Remove Programs. Why exactly don't you want to include the file in subsequent updates? If it's a static file then patches and upgrades won't try to update it anyway if it hasn't changed. Otherwise don't use an MSI package to install it. Pack it in the Binary table of the first install, or as a resource in an exe so that Windows doesn't directly install and control it. You'll have to remove it at uninstall time. >> I don't want the user to have to download the larger MSI file (actually I turn it into an exe) that contains the static file when they do an upgrade, since there's no utility in doing so. I'm not sure what you mean by "Pack it in the Binary table of the first install". I'm not that knowledgeable about MSI's in general, have always used the .NET setup until I started using Wix. Phil Wilson -----Original Message----- From: Wix Mailing List [mailto:w...@danhinsley.com] Sent: Tuesday, May 18, 2010 9:41 AM To: 'General discussion for Windows Installer XML toolset.' Subject: [WiX-users] Upgrade installation The install of my app includes a large file that I don't want to include in the subsequent updates. So I have an install project and an upgrade project. I have the Product->UpgradeCode, and the Component->GUID Guids the same in the install and the upgrade. I use AutoGen for the Product and Package ID's. I run the install, then the update. Everything works OK, except there are now two entries in the Add/Remove program list. When I did this using the .NET install, it only kept the latest in the list. Any hints on how I would go about doing this? Thanks, Dan ---------------------------------------------------------------------------- -- _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at Portland House, Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77 . You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). ---------------------------------------------------------------------------- -- _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at Portland House, Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77 . You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at Portland House, Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77 . You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). ---------------------------------------------------------------------------- -- _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
