For major upgrade case: yes. The easiest way is to use generated component guids (when the keypath's name changes (or the directory "chain" changes in the case of filesystem keypaths) the computed guid will differ, and changing the guid means (from the POV of Windows Installer) that you deleted the old component and created a new one. That is why you don't share unchanging resources with other resources that change in the same component). For the minor upgrade case: will it hurt your product to leave the dll_ver1.dll in place and simply not use it and place the dll_ver2.dll SxS? At least until your next major upgrade? Blair > Date: Sun, 30 Jun 2013 21:10:18 -0700 > From: phogl...@rimage.com > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Update: Best Practice? name of dependency changes in > update > > After posting the above question, I thought maybe I should post the 'answers' > that I have been contemplating based on the research I have done. > > Assume will always do Major Upgrade > 1) in Release 1.0 create a component for dll_ver1.dll. > > 2) In Release 1.1 > a) delete the component for dll_ver1.dll from the project. > b) create a new component with the new dll_ver2.dll. > > Expectation is that since the product will be removed, the dll_ver1.dll will > be uninstalled and the new dll installed as part of the new product install. > This seems like the most straight forward idea but it locks use into only > doing major updates. > > If we want to also be prepared to do minor updates. > 1) in Release 1.0 > a) create a component with a registry key as the key path, or possibly > another file dll/exe which has a version to increment for each update. > b) add dll_ver1.dll to this component. > > 2) in Release 1.1 > a) remove the dll_ver1.dll from the component. > b) add a RemoveFile for dll_ver1.dll. > c) add dll_ver2.dll to this component. > d) make sure the version of the keypath file has changed. > e) if registry key used as a keypath then need to set component as > transient???? > > So I am not sure if the above analysis is correct or 'best practice' and I > am certainly open to researching any other approach. > > thanks for any suggestions. > Phill > > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Best-Practice-name-of-dependency-changes-in-update-tp7587023p7587024.html > Sent from the wix-users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows:
Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
