Added to bug tracker (#3468329)
Klaus
-Ursprüngliche Nachricht-
Von: Rob Mensching [mailto:r...@robmensching.com]
Gesendet: Sunday, 1. January 2012 21:04
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [WiX-users] Burn: Is it possible/supported to bootstrap Windows
That looks like a bug. There needs to be callbacks on the elevate call
because all "action" (Detect, Plan, Elevate, Apply) calls are async.
Additionally, there should be callbacks when elevation happens durin Apply.
Note: You don't need to explicitly call Elevate() because it will happen if
necess
Can you provide more detail? I'm not sure how to interpret the question.
On Wed, Nov 30, 2011 at 2:55 PM, David L. Beckwith wrote:
> Is there a list of possible error responses when using the -layout command
> with the burn app? I tried digging through the source without much success
> and hope
If you enable feature selection (MsiPackage/@EnableFeatureSelection) then
Burn should fire callbacks on feature detection and planning.
Note: EnableFeatureSelection is off by default because managing feature
states in the Windows Installer can be very tricky.
On Tue, Dec 20, 2011 at 1:36 PM, shru
I don't know what this is:
You must be using some other bootstrapper not Burn provided by the WiX
toolset. I recommend following up with the vendor that provided you that
bootstrapper.
On Mon, Dec 19, 2011 at 9:41 AM, Wang, Miaohsi wrote:
> Hello All,
>
> In our bootstrapper we are using a R
This sounds like a bug related to Burn's relatively new code to suppress
restarts while it is running. Can you please open it with this information?
On Thu, Dec 15, 2011 at 12:10 PM, Roy Chastain wrote:
> I just wanted to put this out there again as an unanswered question. I
> am sure there is
Take a look at Burn in WiX v3.6. It handles all this stuff correctly.
On Mon, Dec 19, 2011 at 1:49 PM, Jordan Dressman wrote:
>
>
>
>
> I'm trying to create a bootstrapper that checks for and installs the .net
> framework 4.0 client profile. (I don't want to ship the 42MB .net
> installer, prefe
The BA can log messages to the bundle log file and the BA gets all the
messages passed from the MSI. Thus it would be possible for your BA to
write MSI error messages to the log file.
On Sun, Dec 18, 2011 at 10:56 AM, Bob Arnson wrote:
> On 13-Dec-11 21:25, Sunny Li wrote:
> > Is there anyway to
Is there a bug trackinng this work? If not, it probably got lost.
On Thu, Dec 15, 2011 at 11:44 AM, Klaus Gütter wrote:
>
> Rob Mensching-7 wrote
> >
> > Burn will support an immediate (aka: forced) restart. You should map exit
> > codes from the MSI4.5 installer using the ExeEngine/ExitCode elem
The .zip file on the Source Code tab is useless because it contains only
information from the "default" branch. The WiX toolset has multiple
branches so the default branch contains only the root common information.
On Wed, Dec 21, 2011 at 6:03 AM, Alan Goode wrote:
> Which download did you get?
10 matches
Mail list logo