[WiX-users] WiX36.exe and Antivirus
The last few builds of WiX 3.6 that I have tried installing have been blocked by my antivirus (Kaspersky 3.6). It detects it as PDM.Trojan.generic. I was just wondering if anyone else's AV has started giving them problems with WiX36.exe lately? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX36-exe-and-Antivirus-tp6879249p6879249.html Sent from the wix-users mailing list archive at Nabble.com. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 3.6.2207.0 and 3.6.2201.0 are missing the data subdirectory.
Is there a way to extract the MSI then? The problem with providing just the exe right now is that it doesn't support installing only select features (like the MSI does). I was thinking that /layout might work but the WiX BA doesn't support that switch (not sure if that extracts embedded stuff anyway). -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/3-6-2207-0-and-3-6-2201-0-are-missing-the-data-subdirectory-tp6873149p6879215.html Sent from the wix-users mailing list archive at Nabble.com. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Uninstall stops Explorer but doesn't restart it
Hi, I have a package with a background process that is normally running. When the user uninstalls the software, Wix and/or Windows Installer prompts to shutdown both the process and Explorer (to unregister extensions) but it does not restart Explorer. I'm sure this is a known issue. Can anyone point me to some solutions/work-arounds for this? Thanks. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] major upgrade from per-client to per-machine install
Hi, (moving this to a new thread) I have an existing MSI that needs to be MajorUpgrade'd from per client to per machine installation.Right now installing the latest bits results in two versions of the program being installed side by side.This does not work for at all. How can I remove the existing per-user installation during MajorUpgrade so that the new per-machine installation can be installed instead? Thanks a lot!Martin -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] RemoveExistingProducts, rebooting, and custom actions writing RunOnceEx
Hi there, I'm new to this list and am writing because I feel like im a Catch-22 situation. I'm maintaining a WiX-authored MSI installer for our company's product which supports major upgrades. In addition to the main product A, we're also installing a standalone application B that checks if all of A's required files have been installed, and have the expected file version, file size etc. B must be run after a successful install, which might or might not require a reboot, and after all installed files have actually been written to their target destinations. The original author of the installer solved this for the reboot case with the following sequencing in the InstallExecuteSequence table (excerpt): - InstallInitialize - [...] - InstallExecute - RemoveExistingProducts - Check if a reboot is required, and if yes, run a CA that writes RunOnceEx key to run B after next reboot; this requires elevated permissions, therefore CA must run deferred - InstallFinalize So far, so good(?). Now for the next major upgrade, the above requirements still hold, while we're now also installing 3rd party .NET assemblies to the GAC whose version is not under our control. This leads to the issue described in http://support.microsoft.com/kb/905238, "An assembly in the global assembly cache or SxS is missing after you perform a major upgrade by using a Windows Installer package". The recommended solution is to schedule RemoveExistingProducts after InstallFinalize. However, (and now comes the Catch-22), while checking whether a reboot is required only makes sense after RemoveExistingProducts, the CA cannot be scheduled after InstallFinalize, because it requires elevation, which in turn requires it be scheduled between InstallInitialize and InstallFinalize. Conversely, if I schedule the CA between InstallInitialize and InstallFinalize, the reboot check might not be meaningful because RemoveExistingProducts has not run yet. I'd be extremely grateful for any ideas or suggestions. Best, Simon -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
