Another way of looking at what John is suggesting is considering that you 
probably want to take a step back a moment and focus more on version 3 and less 
on version 2. You're looking at some sort of super-linear number of 
installations you're going to have to support; all those permutations on top of 
what is already a matrix of install testing that needs to be done means you 
could be talking somewhere in the order of 10,000 different tests for just a 
couple of operating systems and configurations by versions 4 and 5. Obviously 
you can't test that much, so it would just be gap in the end result.

Version 2 is the easy part. The hard part is asking the age-old question, "What 
if more than 1 person did this?"

Specifically, the answer may lay in focusing on what the wording of the word 
"support" means. Does adding users to version 1 affect version 2? Permissions? 
Maybe those questions might make it easier - but I advise not going through 
with scenario-based installers. :-)
 
-----Original Message-----
From: Pavan Konduru [mailto:pavan.kond...@accelrys.com] 
Sent: Thursday, March 6, 2014 1:19 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Upgrade and side by side with the same installer

Hi John,

Thank you for your inputs.
Looks like things would get pretty complicated when Hotfixes and patches will 
be involved.
The problem is the product architecture supports different versions residing 
side-by-side. Been pulling my hair out to see how to make this work.
How about creating 2 installers, one which does a side-by-side and one which 
would do an upgrade. The bootstrapper checks for existing product and give an 
option to user for upgrade/side-by-side. Call the appropriate installer based 
on User selection?

Is this feasible? It would surely involve a lot of redundant code and 
maintenance.

--Pavan


-----Original Message-----
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Wednesday, March 05, 2014 2:48 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Upgrade and side by side with the same installer

No (it's not a good architecture).  Major Upgrade mostly works really well and 
can be fully automated.  Side-by-side converts it to a manual process.  You're 
also going to have to maintain a set of patches for each release (really, each 
separate product, since you're going to have to have separate upgrade code 
GUID's to  make this work).

Of course, there are plenty of products out here that execute this model, 
including several from Microsoft.  But popular doesn't mean good.

With each new "version" that can run side-by-side with all the others, you're 
going to have a factorial increasing load for your QA team trying to figure out 
(and stamp out) all the interactions.  Same goes for each installer, each 
patch, each upgrade, etc.

--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com



-----Original Message-----
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Wednesday, March 5, 2014 4:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Upgrade and side by side with the same installer

Best I could think is to use Burn and make each install able to side by side 
install, and conditionally remove the old copy based on user input inside a 
custom BA.. You'd lose the major upgrade goodies of Windows Installer, but it 
should work.

-----Original Message-----
From: Pavan Konduru [mailto:pavan.kond...@accelrys.com]
Sent: Wednesday, March 05, 2014 3:04 PM
To: General discussion about the WiX toolset. (wix-users@lists.sourceforge.net)
Subject: [WiX-users] Upgrade and side by side with the same installer

Hi All,

Is it possible to create an installer that would do an upgrade or side-by-side 
based on the user input?
Say we have 1.0 installed. When the user runs a version 2.0 of the same 
product, give him a choice to either upgrade the existing or install as a side 
by side.

Is it a good architecture to even allow this?

--Pavan
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the 
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the 
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are 
intended exclusively for the individual or entity to which it is addressed. The 
message, together with any attachment, may contain confidential and/or 
privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution is strictly prohibited. If you have received this message in 
error, please immediately advise the sender by reply email and delete all 
copies.


------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the 
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the 
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.


------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to