[wix-users] (deprecated) Sub-Folders not updating install location correctly
I am having trouble getting my installation to work correctly. In my installation, the user needs to select 3 paths, the Program Installation folder, the Local data folder, and the Server data folder. The Local and Server data folders can be shared, or separate folders depending on the user. I have got the install to allow to select all three folders, and the properties are getting updated, but for some reason, it is not updating the sub-folders of my Server data folder. However, both the Program install and the Local data folders are updating correctly, and I am totally stumped as to what is happening. If anyone can help I would sincerely appreciate it. I am including copies of the WXS files as well as the relevant portion of the log file to help to try to determine what the problem is. I am assuming that the user is performing a full UI install, at the present point in time. I may allow for Minimal UI and Administrative installs later, but I need to get it working with the Full UI currently. I removed all GUIDs from the files and inserted "YOUR_GUID_HERE" instead. I also anonymized the folder names. I have attached the section of the install log showing where the local data folder path was updated, but the server data sub-folders were not, at the end of the message. WIX_UICustom: http://schemas.microsoft.com/wix/2006/wi";> 1 1 1 1 NOT Installed AND NOT PATCH Installed AND PATCH 1 1 WixUI_InstallMode = "InstallComplete" WixUI_InstallMode = "Repair" OR WixUI_InstallMode = "Remove" WixUI_InstallMode = "Update" 1 1 1 1 The relevant portion of my Directories.wxs: http://schemas.microsoft.com/wix/2006/wi";> . . . . . MyInstallDirDlg.wxs: http://schemas.microsoft.com/wix/2006/wi";> 1 Installed Installed 1 1 1 Installed Installed Installed Installed 1 1 1 Installed Installed Installed Installed 1 1 1 Installed Installed Install Log: (UNKNOWN) Action 11:06:51: WelcomeDlg. (UNKNOWN) Action start 11:06:51: WelcomeDlg. (UNKNOWN) Action 11:06:51: WelcomeDlg. Dialog created (CLIENT) MSI (c) (58:14) [11:06:51:374]: Note: 1: 2205 2: 3: _RemoveFilePath (CLIENT) MSI (c) (58:14) [11:06:51:389]: PROPERTY CHANGE: Modifying CostingComplete property. Its current value is '0'. Its new value: '1'. (CLIENT) MSI (c) (58:14) [11:06:51:389]: Note: 1: 2205 2: 3: BindImage (CLIENT) MSI (c) (58:14) [11:06:51:389]: Note: 1: 2205 2: 3: ProgId (CLIENT) MSI (c) (58:14) [11:06:51:389]: Note: 1
Re: [wix-users] (deprecated) (deprecated) Difxapp Component Installation condition
Ok, I'll modify my MSI accordingly... Thanks for the advice.. -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: July-22-2015 4:59 PM To: wix-users@lists.sourceforge.net Subject: Re: [wix-users] (deprecated) (deprecated) Difxapp Component Installation condition I think it would be advisable to follow the one-resource-per-component pattern. http://stackoverflow.com/questions/1602831/wix-one-file-per-component-or-sev eral-files-per-component -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-deprecated- Difxapp-Component-Installation-condition-tp7600925p7600926.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[wix-users] (deprecated) Does parent of a companion file always need to be from same feature?
I’ve been facing issues while updating a few companion files in a windows installer patch for which size does not change but checksum does change. I'm not going into details here because I know why bug happened and what was the core reason. The problem is that I went to MS paid support and they say that for companion file logic to work companion and its parent must be in the same feature. If parent and companion are in two different features then it is not a supported scenario. The documentation on MSDN does not say that both files must be from same feature. They also said that they won't document this on MSDN because anyone with basic installer knowledge will know it already. I don't consider myself a beginner and didn't know it. So I have come to the experts here (some of whom have probably earlier worked with MS on core installer engine): “Is it really mandatory that companion and its parent should always be in same feature”? How do I take advantage of companion file logic if my feature does not have any versioned file? Thanks and Regards, -kashif -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[wix-users] (deprecated) Wix book as a free ebook from Packt Publishing - today only
https://www.packtpub.com/packt/offers/free-learning -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-book-as-a-free-ebook-from-Packt-Publishing-today-only-tp7600930.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
