Commandline parameters are case sensitive when setting up overriable variables
and passing them to an MSI using the stdba.
Is there a way around this? i.e. How to we recognize command line parameters
coming in where case doesn't match?
Thanks.
Darwin
---
>
>>>First, the progress bar in the MSI UI doesn't show any progress while
>>>it
>is installing. It this universally >>the case? Has anyone else seen this?
>
>
>I'm also having this issue, are there any solutions?
>
>
>Thanks
I've found a kludge that has seemed to work so far. It is bound to cause
Working with build 2928, it seems that the burn engine adds an entry that is
visible in "Programs and Features" too soon.
It adds it there before anything is installed.
It can get you into some weird states.
Scenario 1: Listed in "Programs and Features" but not installed
There comes a point in
There are 2 issues that I'm wondering about with the "DisplayInternalUI" set to
Yes in my MsiPackage bundle.
First, the progress bar in the MSI UI doesn't show any progress while it is
installing. It this universally the case? Has anyone else seen this?
Second, there is no item in the task bar
I wanted a simple launch condition in the bootstrapper to check and make sure
that .net 3.5 is installed. I realize that I can make a PakageGroup, but I
don't want to install it if it isn't there.
I cannot find a way to reference the NETFRAMEWORK35 property.
It looks like the bal Condition only
Burn seems really strict on enforcing reboots.
You can't uninstall after an install until a reboot happens when it is
"required". It also goes the other way when you uninstall, you can't re-install
without a reboot.
It looks like what controls this is found in \src\burn\engine\registration.cpp.
ay, July 12, 2012 3:44 PM
To: General discussion for Windows Installer XML toolset.
Cc: Darwin Baines
Subject: RE: BalExtension and the Common Public License
Sensitivity: Personal
Out of pure curiosity, why would you need to do your own custom bootstrapper?
The WiX Burn bootstrapper is incredibly f
I am looking into possibility of creating my own bootstrapper that tweaks the
standard bootstrapper.
I assume that if I write my bootstrapper from scratch, I shouldn't run into
complications, but if I start with the standard bootstrapper code and make some
changes that fits my situation, I've c
https://sourceforge.net/tracker/?func=detail&aid=3542020&group_id=105970&atid=642714
Date: Tue, 10 Jul 2012 00:28:17 -0400
From: Bob Arnson
Subject: Re: [WiX-users] Should balinfo.h be included in sdk/inc?
On 09-Jul-12 17:26, Darwin Baines wrote:
> You can't bu
I just figured out how this works looking through the WixStdBA source code.
This was implemented in time for the RC release on May 21.
(https://sourceforge.net/tracker/index.php?func=detail&aid=3489809&group_id=105970&atid=642714)
To pass command line arguments, it goes something like this:
You can't build WixStdBA without balinfo.h.
Should it be included in the binary distribution under sdk/inc?
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat land
I am having a problem with an uninstall that rolls back and crashes on 64 bit
Wix 3.5 setups.
We get the following error message in the Event logs:
00 ntdll!RtlReportCriticalFailure(long StatusCode = 0n2, void * FailureInfo =
0x07fe`0023)+0x62 [d:\win7sp1_gdr\minkernel\ntos\rtl\rtlutil.
12 matches
Mail list logo
