Cryptonomicon wrote: > I am putting together a package of number crunching code that will be opened > sourced and I need to run parallel versions. I envision that users will be > running the validated release version and may also be playing with a non > validated version (by validation i mean the number crunching routines > produce the right numbers - which look remarkably like the wrong answers) > > So what I need to do is come up with a process via which users can install - > remove - upgrade etc one version and not touch the other. In fact I could > see production users who have been roped into UAT in other scenarios may > need parallel versions running on the same machine without a risk of the > test application frying production data. >
If you need a couple of different instances, you can produce multiple packages with different product and package codes. If you need to support more instances, take a look at the MSI SDK for "multiple instances" to see how you can use instance transforms to simplify the process. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
