Thanks for the responses. In particular, I didn't realize the newer redist
packages can be safely run without detecting them before-hand. It seems
like this could still be a problem for people who are not compressing the
redists, but that is not my scenario.
I also discovered this blog post which
You might want to look at this recent thread.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/V-C-2013-redist-detection-td7596368.html#a7596373
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-FileSearch-in-64-bit-system-folder-t
Hi Dave,
I have done this with a different Approach.
I have used an Msi Product Check to Check for existing redist Packages.
To make sure the 64Bit Versions are not installed set the 64Bit flag within
burn.
I search for product ids with Microsofts Old Manifest bootstrap Editor. Don't
know if th
I am trying to write the detection logic for some VC redist packages (32
and 64 bit). The problem I am running into is being able to detect the
assemblies under windows\system32 on a 64 bit OS.
On a 64 bit OS, it appears that burn translates these as such:
[SystemFolder] => C:\Windows\system32\
[
4 matches
Mail list logo