I am using wix 3.9.721 and vs2013 (or vs2010).
When I build a project (without making any changes to the source files:
In the case of a MSI project there is no change to the output file.
In the case of a Bundle, the output file is updated, the ProductId changes,
but the version is the same as th
The point is that vcredist installs side by side, lots of applications are
dependant on it, so it shouldn't be removed, but there is newer a problem
installing one, even if there is one or many from before.
On Fri, Aug 15, 2014 at 8:19 PM, Jeremiahf wrote:
> "In fact, I recommend against using
"In fact, I recommend against using any search for the VC runtime. They
use the WixStandardBootstrapperApplication/@SuppressDowngradeFailure
option, so you can safely always chain your desired VC runtime version.
If it's outdated, nothing happens."
So this is def a bad way to handle this even thou
No solution to the repair and uninstall MSI UI yet. Non-trivial problem. If
there isn't a feature request tracking it, you might open one so then you can
track its progress (or lack thereof).
___
FireGiant | Dedicated support for th
has there been any update since this post, is it possible to use burn with no
UI?
I would like to be able to repair and uninstall using the MSI UI instead of
the burn UI
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bootstrap-a-single-MSI-n
Thanks guys but I need to detect if it is installed through an msi and not
a bootstrapper. It also has to be the x86 version.
I was trying to detect it through the registry as I have done for previous
versions of V C++ Redists. Any idea's?
Sorry for the lack of info in my initial email.
Thank you
Bob; Thanks for the advice. Sorry for posting incorrect x64 code in the
first post.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/V-C-2013-redist-detection-tp7596368p7596376.html
Sent from the wix-users mailing list archive at Nabble.com.
7 matches
Mail list logo
