I'm running into an issue where our install is setup to include version X of the VC8 CRT assemblies using the merge modules we have checked into our repositories, however the code is being built against a newer version Y. The assemblies won't work when installed on a test machine because they are requiring version Y while the installer is laying down version X because of the merge modules. We are getting prepared to release our initial installer which will be an MSI and future releases will be MSPs.
My question is as follows: Let's say we include the merge modules for the newer version Y into our initial MSI release. What would happen if we had to upgrade to an even newer version Z down the line because of a security update and wanted to include that in our install? How would that impact patching since all of our updates are released as MSPs? ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
