The "easy" answer is to install one instance of the application, and have on first run the user enter an activation code. This code would then enable all the functionality available for that specific code.
-----Original Message----- From: Tad Carlucci [mailto:tad.carlu...@gmail.com] Sent: Monday, June 17, 2013 8:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to handle multiple versions Yes, there are three different upgrade guids already. At this point I have it so I can install all three versions and they'll upgrade themselves and prevent downgrades. I need to keep it to only-install-one-of-the-three and would greatly prefer to avoid the support issues which would arise after switching from a higher flavor to a lower. Using a custom registry key seems a wasteful duplication of effort. So, let's not talk about the way Microsoft would do it, OK? I did find some of the pile of words about the installer which talked about the upgrade table. But other than the fact that it's there, nothing more. For each flavor, I know the upgrade guids for the other two. But there is nothing about how to tell if any version of them is installed. And I didn't find anything about forcing an un-install for a given upgrade guid other than the current package's. So, how does one go about actually using the upgrade table. And, having found you want to un-install some other package, how do you do that? On Mon, Jun 17, 2013 at 2:00 AM, Philip Patrick <patri...@varonis.com>wrote: > I would start trying to use 3 different upgrade codes and using > Upgrade table to prevent installation of "lower" versions of the > product. My concert in this approach - not sure if upgrade from Lite > to Basic to Premium will work smoothly - just need to find it out empirically. > > If it won't work - can add some registry key that will say the current > installed type (Lite/Basic/Premium) and LaunchCondition will check it > and prevent unwanted downgrades. Or maybe file search to search for > specific file that does not exist in higher versions. > > > > -----Original Message----- > From: Tad Carlucci [mailto:tad.carlu...@gmail.com] > Sent: Monday, June 17, 2013 07:01 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] How to handle multiple versions > > Can someone point me in the direction to reach this goal: > > My requirement is for three flavors of the application: Lite, Basic, > and Premium; each released as a separate MSI package. > > The user can only move up the chain. For example, if the Basic is > installed, Lite cannot be installed. If, in the future, that user > installs Premium, any Basic installation must be removed. > > Updates will be synchronous, bumping the version numbers of all three > packages at the same time. Thus, if the user has Basic 1.2.0 > installed, the user may install any later version or Basic, or switch > a Premium version 1.2.0 or later. But that user can not install any > Lite package, or any earlier Basic package. > > ---------------------------------------------------------------------- > -------- This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ---------------------------------------------------------------------- > -------- This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
