We have a somewhat unique requirement for our product. Concurrent versions need to be made available on a single machine. We have a matched client and server, for which the protocol changes each version. One desktop machine might need to talk to 5 differently-versioned servers, and will need 5 versions of the components.
A server hosts a website with a link to the installation package, so obtaining the server-specific version isn't an issue, so I don't know if a patch will work. What is an issue is that the versions might be installed in any order. The server's website will then use object tags with hardcoded CLSIDs to launch the version-specific components. This currently works with Internet Component Download, since it creates the CONFLICT.# directories. All versions need to have a few common files in %system32%. These files might get upgraded in a future release, but will retain their binary compatibility. All versions of the product need to show up as one Add/Remove programs entry, and this is the tricky part for me. Removal of that one program needs to remove all versions currently installed, and all registry that's been affected by several overlapping COM components. If it wasn't for this requirement I would happily create a different product UUID each time, since that's essentially the behavior we want anyway. Anybody have suggestions on how to proceed? Thanks, -Bryan ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
