Re: [WiX-users] Advertised feature install starting
John Hall wrote: However, this installing per-user on demand could be quite useful. I would like to install some files per-user as well as the registry entries. How do I make sure the files that need to be installed are available? That requires caching the real MSI and any external cabs. The .msi file that MSI caches is stripped of all embedded cabs. Bob, Is that something I would have to do manually, or is there an MSI mechanism? Regards, John - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Advertised feature install starting
John Hall wrote: Is that something I would have to do manually, or is there an MSI mechanism? The former or both: MSI doesn't cache full MSIs, so that you have to do manually. If you run the install from the full copy and don't delete it, MSI will use it during source resolution. Otherwise, you can use the MSI APIs to add the cached copy to the source list (e.g., MsiSourceListAddSource). -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Advertised feature install starting
John Hall wrote: It's an HKCU registry key that would have been created for the user who installed the application, but obviously not the user who is running. Is this the default behaviour for a key in HKCU even if the feature is not advertised? Yes, for an advertised shortcut. Also, is this the expected behaviour? I thought that a copy of the MSI was stored away in c:\Windows\Installer, so why is the system not able to use that one rather than looking for the original .msi file that the bootstrapper dropped into the temp directory. It does but something's requiring source. You can set the MSI logging policy to get a verbose log when the repair is triggered. Bob, Thanks for that - I tracked it down to a component that just contains some HKCU registry entries, and so now I understand what is happening. This was triggering a repair install. The repair install was trying to reinstall some files that were marked as companion files. It turns out that I don't need to have them as companion files any more so I've changed that and the install no longer prompts for the media and all is well. However, this installing per-user on demand could be quite useful. I would like to install some files per-user as well as the registry entries. How do I make sure the files that need to be installed are available? Currently, I have a bootstrapper that includes the .msi and .cab files as resources - it drops them into the temp directory and then deletes them again once the installation has completed. I tried including the per-user files in their own cab file and embedding them in the .msi, but this doesn't work. Regards, John - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Advertised feature install starting
Hi, I am trying to build the 'toolsrc' project for WIX version 3.0. I already have windows SDK version 6 installed but it failed to build MsgGen tool because of the following error: WixBuild.Common.targets(129,5): error : Please install the Windows SDK version 6000.0.0 (Windows Vista) or higher. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Advertised feature install starting
John Hall wrote: *However, this installing per-user on demand could be quite useful. I would like to install some files per-user as well as the registry entries. How do I make sure the files that need to be installed are available?* That requires caching the real MSI and any external cabs. The .msi file that MSI caches is stripped of all embedded cabs. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Advertised feature install starting
I've got some machines that after a minor upgrade, unprivileged users unexpectedly get MSI launching a dialog saying that the feature you are trying to use is on a network resource that is unavailable. Administrators do not see the message. The installer was run as Administrator. I assume it is because some features have been installed as Advertised rather than Local. In my installer however, I have marked all my features with AllowAdvertise=no, so It's probably an automatic repair. Check the System event log to see which component MSI thinks is broken. Bob, Thanks for the pointer. It's an HKCU registry key that would have been created for the user who installed the application, but obviously not the user who is running. Is this the default behaviour for a key in HKCU even if the feature is not advertised? In this case, it doesn't matter if the settings are not available for the current user, and I would prefer MSI just to ignore these keys. Also, is this the expected behaviour? I thought that a copy of the MSI was stored away in c:\Windows\Installer, so why is the system not able to use that one rather than looking for the original .msi file that the bootstrapper dropped into the temp directory. Regards, John - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Advertised feature install starting
John Hall wrote: It's an HKCU registry key that would have been created for the user who installed the application, but obviously not the user who is running. Is this the default behaviour for a key in HKCU even if the feature is not advertised? Yes, for an advertised shortcut. Also, is this the expected behaviour? I thought that a copy of the MSI was stored away in c:\Windows\Installer, so why is the system not able to use that one rather than looking for the original .msi file that the bootstrapper dropped into the temp directory. It does but something's requiring source. You can set the MSI logging policy to get a verbose log when the repair is triggered. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Advertised feature install starting
I've got some machines that after a minor upgrade, unprivileged users unexpectedly get MSI launching a dialog saying that the feature you are trying to use is on a network resource that is unavailable. Administrators do not see the message. The installer was run as Administrator. I assume it is because some features have been installed as Advertised rather than Local. In my installer however, I have marked all my features with AllowAdvertise=no, so The bootstrapper has since deleted the .msi and .cab files - if I put them where MSI is looking for them (in Administrator's temp directory) then everything works from then on. Does anybody have any ideas why this might be happening or how I might go about tracking it down? I don't even know which feature it is that is being looked for, since the installer starts while the application is running, not right at the start. Thanks, John - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Advertised feature install starting
John Hall wrote: I've got some machines that after a minor upgrade, unprivileged users unexpectedly get MSI launching a dialog saying that the feature you are trying to use is on a network resource that is unavailable. Administrators do not see the message. The installer was run as Administrator. I assume it is because some features have been installed as Advertised rather than Local. In my installer however, I have marked all my features with AllowAdvertise=no, so It's probably an automatic repair. Check the System event log to see which component MSI thinks is broken. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
