Re: [WiX-users] Getting ProductVersion of an msi from wix

Thanks Nir for the response! As I mentioned, the ProductCode in my case is changing with every new build of the msi, so I cannot search for it as it's not fixed. I was looking into RegistrySearch and found conflicting info for the Result attribute which is an Enumeration. The documentation says

Re: [WiX-users] Getting ProductVersion of an msi from wix

I also tried using util:FileSearch giving it the path of one of the files this msi installs but turns out that the Path attribute doesn't takes an absolute path(complains of ':' in the Path). My source code for building this setup bundle lies in a different drive than the drive where this file

Re: [WiX-users] Getting ProductVersion of an msi from wix

Hi Phil, Comments inline for your queries: /It might help to say why you want to do this and what problem it solves./ I need to add a blocking condition based on whether a particular msi is installed or not and hence I need a way to figure out whether that msi is installed or not. /You don't

Re: [WiX-users] Getting ProductVersion of an msi from wix

Ok Let me try this time to state the problem:) We have a legacy setup installer(based on wix 3.0) that installs the core engine features. We are developing a new setup installer(based on wix 3.8) that installs tools features. Based on the current code they both share a common msi(which is

[WiX-users] [SPAM] Registerting WMI interface through Burn

Hello All, As part of our product install, we need to register a WMI interface by running mofcomp tool on a .mof file. I'm trying to find the best way to handle this in Burn that could do this for me. Can anyone suggest any options? Regards, Rajesh -- View this message in context:

[WiX-users] Signed version of burn.exe in Wix 3.8

Hello All, I'm running into issues with the signing of my burn installer and I was wondering if I can have the Burn.exe(in x86 location) signed beforehand and replace the unsigned version in my wix toolset location. That way if I just sign the burn installer, that should have the burn engine

[WiX-users] Signing issue with Burn installer

Hello All, I've been trying to sign my Burn installer by following http://wixtoolset.org/documentation/manual/v3/overview/insignia.html I'm using Wix 3.8.1128.0 I've overridden the 2 targets as follows: Target Name=SignBundleEngine Exec Command=Signtool.exe sign /a

Re: [WiX-users] Signing issue with Burn installer

Thanks Phill for the response! Using quot;%(SignBundleEngine.FullPath)quot; and quot;%(SignBundle.FullPath)quot; returned the same value. I'll work on getting the right command line versions of sign tool but unless I resolve the above issue, it will not work. Does the file generated by running

[WiX-users] Detecting Windows 10 OS in Wix

Hello All, One of our codebases is on Wix 3.6 and we are using built-in Wix variable VersionNT to detect the OS version. The check we are doing is : (VersionNT v6.3) This should return true on Windows 10 but it's returning false. Looking at the Wix logs VersionNT is set to 6.3.0.0 and that

[WiX-users] Warning condition in Standard BA

Hello All, I've started working on the Wix Burn installer(on Wix 3.8) and have been loving it so far! I had a quick question: Is there a way to add a non-blocking condition(warning) using the Standard BA to warn the user of any condition but not necessarily block him from proceeding further.