My preference would be to have the new MSI only include the new files, however we could include older versions if necessary. Ideally the versions in the GAC would stack up until someone uninstalls them. If we could pull it off I would like to have one entry in add remove programs that gives the option of removing a specific version or completely removing all of the installed versions.
Correct. File names and paths for VS support stay the same. Preference would be to release a single MSI that can be run from windows. Mike -----Original Message----- From: Blair [mailto:os...@live.com] Sent: Thursday, September 24, 2009 5:27 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Update adding a new compontent I assume from the description you don't want to ship the older versions you intend to leave behind in newer MSIs, correct? Will those old components ever be removed? If so, by what mechanism? The component you update (that is the DLL, Debug, Doc, and Registry, correct?) keeps its filename and directory, correct? Are you intending to simply ship the raw MSI file out, or are you bootstrapping it? -----Original Message----- From: Stout, Mike [mailto:mike.st...@oa.mo.gov] Sent: Thursday, September 24, 2009 1:06 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Update adding a new compontent I am new to writing set up packages in general and I am looking for a way to have a single file installer that will work as both a clean install and an update to previous installs. The catch is that in update mode I need to change an existing component, add a new component, and leave a third in place. Example: We have an installer for a framework library. One component drops a copy of the DLL into the GAC. Another component writes the DLL, Debug and Documentation files to an install directory and adds a registry entry telling Visual Studio where to find them. Now when it is time to update we want to add the new version to the GAC (new component) without removing the original version(leave existing component), but overwrite the files VS uses with the new version (update existing component). The approach seems to have gotten me closest is to change the ID of the GAC component with each revision while leaving the ID of the VS component static. However to get this to work I am also having to change the product ID which results in each update having its own entry in add/remove programs. Am I on the right track with this? Is there a simple way to get this type of behavior without having to change the product ID? Mike ------------------------------------------------------------------------ ---- -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
