If the only changes in your bug fix are files in the file table, that should work. To rebuild your code you may consider using dark on your released MSI to get your base WIXPDB and to get your starting point for your bug fix.
The REINSTALL property will be autoselected to be the smallest section of already installed features that cover all of the database changes contained in the patch if you don't override it (as you are proposing). Normally the default value should suffice, unless you have a complex feature/component tree or if you have files that don't lend themselves well to the file versioning rules. Your overridden value for REINSTALLMODE property will prevent application of registry and shortcuts from the patched view. If you don't have a requirement for the "a" flag, the default should suffice. Blair -----Original Message----- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Wednesday, February 01, 2012 12:26 AM To: wix-users@lists.sourceforge.net Cc: alex...@qualisystems.com; rone...@qualisystems.com Subject: Re: [WiX-users] How does Torch decide which files changed?! Hi, After all your help :) I think I have a solution to my problem, please let me know what you think: My product is already installed on customers machines, I didn't save the wixpdb nor the files.wxs (the Heat harvest file) of those releases, since I didn't know I'll need them to issue a patch, I also don't have the product Id since it's * (auto generated). So, I need to rebuild my code and create the MSIs again with the same code as the released product making sure I hard code the Original Product Id I take from the released MSI. Then I make my changes (fix the bug or whatever) and rebuild my code and create the MSIs again MAKING SURE to use the same files.wxs created by the previous HEAT harvest (so the GUIDS will be the same). Now I have both wixpdb files without the change and with the change. I torch them to get the diff.wixmst. (using the -xi and -p flags) And then I pyro. (pyro.exe patch\patch.wixmsp -out patch.msp -t RTM patch\diff.wixmst -v) The customer needs to install the msp with this command: MSIEXEC /update "\\tomer-c-d3\Share\patch.msp" REINSTALL=ALL REINSTALLMODE=a It seems a bit cumbersome, will it work? :) Thanks again. -----Original Message----- From: Blair [mailto:os...@live.com] Sent: Monday, January 30, 2012 9:51 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] How does Torch decide which files changed?! One way to see what the transforms in a patch actually contain WRT any particular MSI, open the MSI in Orca, then open the MSP file using the Transform menu item "View a patch". It will highlight the database changes, and in the case of files, you can look at the two file-related tables to see which files it thinks have been changed. -----Original Message----- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Saturday, January 28, 2012 10:59 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How does Torch decide which files changed?! One more thing, I opened the msp file with z7, there are only: exe dll (.net assemblies) and one txt file!? there. -----Original Message----- From: Blair [mailto:os...@live.com] Sent: Friday, January 27, 2012 10:24 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] How does Torch decide which files changed?! Torch marks up the database changes. Including -p causes it to leave the unchanged portions of the database intact so they will be present for Pyro to use in its processing. It is Pyro that looks at the two files and determines if they are the same or not, and it "promotes" files that compare as different to be considered as "changed" and thus be included with the other marked database changes. If you use WIXOUT or WIXPDB files then fragment boundaries are considered in the comparisons, so if you specify references to things to include in your patch family/families, things that are not in any referenced fragments are ignored (by design). Look for the files you are concerned with in the WIXMST file. You should find either paths or references to cabinet-ids for both the updated and the previous versions of the files. Blair -----Original Message----- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 26, 2012 7:19 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How does Torch decide which files changed?! I'm creating a patch, I'm not sure that the patch includes all of my files even though I'm passing the -p flag to the torch.exe. Can someone please explain to me the logic that torch uses to determine what files are included in the patch. Thanks. ------------------------------------------------------------------------ ---- -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ---- -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
