Re: [WiX-users] Update: Best Practice? name of dependency changes in update

2013-07-02 Thread Phill Hogland
Thanks for your comments. Yes I had thought about leaving the old DLL when patching and deal with it on the next MajorUpgrade. I think in most cases we should be able to take that approach, if we use a patch. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n

Re: [WiX-users] Update: Best Practice? name of dependency changes in update

2013-07-01 Thread Blair Murri
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 po

[WiX-users] Update: Best Practice? name of dependency changes in update

2013-06-30 Thread Phill Hogland
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 fro