In that situation, and assuming you have a robust file versioning
scheme, in all these cases you go ahaead and install the MSI anyway
and:
1. Package versions of those files that have lower file versions and
will therefore not update the existing higher versioned ones.Apply
component rules, and
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
To me at least that's not the problem you're describing - that's a
restatement of your solution, the implementation of which is to block
an MSI install if another product is already installed. Anyway, it
looks like you'll need to write code to do this as outlined earlier
based on detection of an
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
Your original problem was I'm trying to detect where a particular
msi is installed or not and based on that I want to block on my burn
setup bundle. but that seems more like a solution to a problem you
haven't described. It might help to say why you want to do this and
what problem it solves. You
Use RegistrySearch on Uninstall Registry Key,
https://msdn.microsoft.com/en-us/library/aa372105%28v=vs.85%29.aspx
DisplayVersion value.
-
Nir Bar
Freelance Developer
Mail: nir@panel-sw.com
Web: www.panel-sw.com
- C++ On Windows, Linux and Embedded Platforms
- 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
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
8 matches
Mail list logo
