I'm trying to think through this installer I'm working on again, and reconsidering how merge modules may be able to work for my situation. If I store the GUIDs properly, then multiple third parties who distribute my module will properly increase the ref count for the components. When all third parties remove their software, the file is removed.
As I deploy new versions of my merge module, and new third parties include them, I may be removing and adding new files. These would result in the components being removed and the ref count being decreased, correct? In which case, upgrading a third party from library Version A to library Version B, might result in the removal of some files from Version A. I think the one remaining piece is figuring how to "not install" a set of components in a merge module based on the existing of a version number set someplace (perhaps the registry) which is > a version known by the merge module. What sort of abilities of WiX could I use to accomplish this? Are there some sort of conditions I can apply to each Component that could implement this check? I'm also having a completely hard time understanding the idea of the "sequence". Where does my merge module fit into this? On Thu, 2007-05-31 at 10:17 -0700, Rob Mensching wrote: > Good question. I have no answer but it is pretty clear that we need one in > the WiX toolset and that's my personal secondary priority when working on WiX > (first priority is keeping the project running as smoothly as possible). > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jerome Haltom > Sent: Thursday, May 31, 2007 10:10 AM > To: Peterson, Joel > Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] upgradable merge modules > > > 1. I really wish > > http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/ was more of > > a how-to. It isn't really intuitive on how to use all of this tooling in > > Visual Studio 2005, or where to find it. > > > > 2. WiX really needs a better bootstrapper as a part of what it offers. > > If it were to have a framework to make a bootstrapper ranging from what > > you see with the Visual Studio 2005, SQL Server 2005, Exchange Server > > 2007, and Office 2007 installers, it'd be golden. > > > > 3. I can't believe a company hasn't come up with a Visual Studio 2005 > > SDK for building highly customizable and interactive bootstrappers. > > My story is that I'm coming to WiX in an effort to create some nice > installers for some ports of some free Unix software to Windows. It > boggles my mind how the official packaging system requires such things > in the first place. I'm actually very surprised that people are in fact > writing boot-strappers. Why doesn't Windows installer support bundling > dependencies? > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
