Hi, I have design question for community. My application has one common dll (common.dll) and two exe applications, where both of them depend on this common dll. Could someone suggest me when I need use minor/major upgrade/patch for each scenario that follows: 1) My group release new version every 2 month. When we are releasing new version, we need to upgrade from previous version, where new version will have additional set of features or some features are removed. It easy requirement, I can uninstall previous version and install new one. 2) In timeslot between old to new version we can find a bug, so we need release upgrade, where this upgrade can contain additional components or some dlls need be updated, When bug founded in common.dll, it can be upgraded for all exe`s that use him. 3) It same like (2) but changes can be done in common.dll, where first exe use new common.dll, but second exe need use common.dll from original version.
Technically (without installer) I know how to support it. Since I don't want to use GAC, I will install 2 exe`s to INSTALLDIR, where common.dll will be installed to INSTALLDIR\Common_X.Y.Z folder. runtime entry in each exe.config will contain <probing privatePath=" Common_X.Y.Z "/> node that will be reference to common folder. So when I will do patch for scenario (3) I will create new folder INSTALLDIR\Common_X.Y.K that will contain common.dll with new version, and for some exe I will update <probing privatePath=" Common_X.Y.K "/>. Thanks in advance Dima ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
