Yeah...iam maintaing command line like.
msiexec -I $(.msi) REINSTALL=ALL REINSTALLMODE=vomus
but it's not working.
Is it mandatory to maintain property tag like
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 30 October 2012 15:32
To: General discussion for
You can change properties in a minor upgrade.
You should describe what your problem is otherwise it's just blind guesswork.
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: 31 October 2012 07:17
To: 'General discussion for Windows Installer XML toolset.'
Subject:
Rob,
I know it can pass parameters but can it conditionally pass MsiProperty
elements only if the value evaluates to something other than an empty string?
Jacob
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, October 30, 2012 10:11 PM
To: General d
Hi all,
I have a product that installs a 32 bit version and 64 bit version installer
(two .msi)
I have a custom action in product.wxs that determines the "bitness" of
Microsoft Outlook (whether the user installed 32 bit or 64 bit version of
Outlook, our product is an add-in).
so I have 2 msi's, b
I imagine that a Burn custom action would be part of the code of a custom
bootstrapper application that would set a variable during the appropriate
event. Could you not use a util:product search or utilL:registry search to
determine which outlook is installed ? Save you a lot of work unless you've
So from your answer it sounds like you cannot really use in
burn?
I have 2007/2010/2013 Outlook and 32 bit/64 bit checking for the bitness isn't
simple, we have a custom action dll that does that for us and returns a MSI
property (which I use in the MSI)
Steve
-Original Message-
From
Nope. You can spot what's allowed in Burn by tracing up through the Parents
section of the help. In the case of CustomAction, the parents are Fragment,
Module and Product. Technically, you can have Fragments in Burn but you'd
expect to see Bundle listed as well if it was.
-Original Message---
Looks like there's a simple registry search. Have you seen this ?
http://stackoverflow.com/questions/2203980/detect-whether-office-2010-is-32bi
t-or-64bit-via-the-registry
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 31 October 2012 16:38
To: General di
Once again Peter, thank you!
Awesome...
STeve
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: October-31-12 12:48 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] custom actions in burn?
Looks like there's a simple reg
There is no such thing as a CustomAction in the context of burn. If you can't
use a combination of the existing searches
(Registry/Component/Directory/Product/File) you either need to extend the
existing BA/UX or write your own, neither of which are trivial.
-Original Message-
From: Pe
I pass "08.11.09.11" to var.InstallerVer, but the version is shown as
"8.11.09.11" in "Control Panel\Programs\Programs and Features". I tried to
create my own preprocessor var like var.ProductVersion and pass
"08.11.09.11" via candle's option -dProductVersion= "08.11.09.11". It
doesn't help. The l
I have a bundle with one MSI that has DisplayInternalUI set to true.
Everything works great during the installation phase: we get all the prereqs
bootstrapped and then we use the already developed MSI UI to gather some
other information. The problem comes up during uninstall: I get the Burn UI
an
Not possible today. Why do you need that?
On Wed, Oct 31, 2012 at 12:57 PM, gy16888 wrote:
> I pass "08.11.09.11" to var.InstallerVer, but the version is shown as
> "8.11.09.11" in "Control Panel\Programs\Programs and Features". I tried to
> create my own preprocessor var like var.ProductVersio
13 matches
Mail list logo
