Re: [WiX-users] How to Prevent 32bit and 64bit MSIs with Different UpgradeCodes and Dynamic ProductCodes from Both Being Installed

Thanks, Phil. Because I do not have a Bundle, which serves as the arbiter for choosing which bitness to install, a user can download each version: 32b and 64b. I think you are able to give them the same UpgradeCode because they will never be able to be installed at the same time due to the Bundle'

Re: [WiX-users] How to Prevent 32bit and 64bit MSIs with Different UpgradeCodes and Dynamic ProductCodes from Both Being Installed

A similar situation: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Registry-Search-in-x86-installers-doesn-t-work-properly-on-x64-machines-td6239779.html -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-Prevent-32bit-and-64bit

[WiX-users] How to Prevent 32bit and 64bit MSIs with Different UpgradeCodes and Dynamic ProductCodes from Both Being Installed

I have two MSIs: one for 32bit and one for 64bit. They contain similar components. 32bit - contains only 32bit components 64bit - contains both 32bit and 64bit components To allow MajorUpgrades, when building the MSIs, the UpgradeCode for each MSI is different, unique, and static. The ProductCode

Re: [WiX-users] Ensure Uninstall When Needed Files are Deleted by User

The EXE and DLL are independent. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ensure-Uninstall-When-Needed-Files-are-Deleted-by-User-tp7596209p7596214.html Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Ensure Uninstall When Needed Files are Deleted by User

Is there an equivalent tool for harvesting registry info for the 64bit dll? 1. One solution is to not let any files self-register. Is there another solution? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ensure-Uninstall-When-Needed-Files-are-D

Re: [WiX-users] Ensure Uninstall When Needed Files are Deleted by User

This could be a good alternative. Though, I remember I could not use heat to harvest a 64bit dll. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ensure-Uninstall-When-Needed-Files-are-Deleted-by-User-tp7596209p7596211.html Sent from the wix-users

[WiX-users] Ensure Uninstall When Needed Files are Deleted by User

My MSI will install a dll and an exe. The dll will self-register. The exe is run by a custom action with a command-line parameter to perform registration and update the registry. The exe can take a command-line parameter to unregister itself and remove references in the registry. How do I ensure

Re: [WiX-users] Editing the CloseApplication Dialog

Now the trouble is getting that change into WiX so that I can build an MSI using this change in wixca.dll which will be used in WixUtilExtension.dll. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Editing-the-CloseApplication-Dialog-tp7595889p759

Re: [WiX-users] Editing the CloseApplication Dialog

Here is the area of interest in the source: static HRESULT PromptToContinue( __in_z LPCWSTR wzApplication, __in_z LPCWSTR wzPrompt ) { ... do { hr = ProcFindAllIdsFromExeName(wzApplication, &prgProcessIds, &cProcessIds); if (SUCCEEDED(hr) && 0 < cProcessIds)

Re: [WiX-users] Editing the CloseApplication Dialog

I may have found the solution. It seems to entail editing CloseApps.cpp in the source then building the WixUtilExtension.dll. http://wix.codeplex.com/SourceControl/latest#src/ext/ca/wixca/dll/CloseApps.cpp http://wixtoolset.org/documentation/manual/v3/wixdev/building_wix.html -- View this messa

[WiX-users] Editing the CloseApplication Dialog

Hello, I am using CloseApplication to check for certain applications running during installation and then to prompt the use to close the applications. There are three buttons that are part of the prompt dialog: Cancel, Retry, and Ignore. I want to remove the Ignore option from the dialog becaus