The ExecutePackageComplete fires when a package is installed, you could load
your control and get the information before returning from that event. But if
you are getting information that influences the other MSI's, you probably
should do 2 Detect, Plan, Apply cycles.
Sean
> Date: Fri, 19 J
Classification: Public
The bundle.wxs is the bootsrapper code file, when you compile it, it creates an
exe
-Original Message-
From: Freedman, Mark P. [mailto:mark.freed...@jhuapl.edu]
Sent: July-19-13 12:44 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-use
Right, My bootstrapper projct creates the exe, and I can run it and install
with it. I'm not sure what's happening to the MsiProperty that I"ve set up. I'm
not sure how to read it from the MSI installer package, and it isn't passed as
a command line argument as shown in the logs.
I thin what I
Classification: Public
Mark,
In my bundle.wxs I have the following:
This way if I don't have a command line argument the MSI property
SERVICESLOGLEVEL is set to WARN by default, hence I can change it by:
MYBOOSTRAPPEREXE.exe SERVICESLOGLEVEL=DEBUG
Then in my produc
On Fri, Jul 19, 2013 at 8:35 AM, Chen, Jianxin wrote:
> “One reason why this CustomAction works from an elevated command prompt
> but not from a non-elevated shell is that the CustomAction is scheduled
> outside of the installation transaction (before InstallInitialize or after
> InstallFinalize)
Some examples:
http://stackoverflow.com/questions/465488/can-i-load-a-net-assembly-at-runtime-and-instantiate-a-type-knowing-only-the-na
http://www.codeproject.com/Articles/32828/Using-Reflection-to-load-unreferenced-assemblies-a
-Original Message-
From: Rahul V [mailto:rahul8...@gmail
Currently, I do not have a custom bootstrapper application, just what I have in
the Bundle.wxs file.
I thought that by setting up the MSI Property that way, it wouldn't require
running the bootstrapper EXE with a command line argument. I just want to pass
a hard coded value of some sort to the
Are you doing a native or managed BA/UX? Is this "control" a native or managed
control?
If it's a native UX/BA and the control is a COM component, you should be able
to create the object after it's installed. If it's managed, you would have to
do some rather involved coding to delay load the a
Hi Jacob,
I was asking you for the details to use which event in BootstrapperApplication
class to interupt the first MSI completion event. After that how can I
start another MSI installation?
Thanks!
On Fri, Jul 19, 2013 at 9:10 PM, Hoover, Jacob
wrote:
> Some examples:
>
>
> http://stackoverflo
Hi, Edwin or Wix Experts,
I had the issue as you mentioned in one of your replies.
"One reason why this CustomAction works from an elevated command prompt but not
from a non-elevated shell is that the CustomAction is scheduled outside of the
installation transaction (before InstallInitializ
Hi Jacob,
I am using managed code, will you please give me more detail?, I am
follwing the below example.
http://bryanpjohnston.com/2012/09/28/custom-wix-managed-
bootstrapper-application/
Thanks!
Regards,
Rahul
On Fri, Jul 19, 2013 at 7:40 PM, Hoover, Jacob
wrote:
> Are you doing a native or m
One option would be to use an immediate custom action that copies the existing
files to the temp folder, and then a semi-custom action which copies those
files to your "backup folder".
-Original Message-
From: Srinu ..., [mailto:srinu_...@yahoo.com]
Sent: Friday, July 19, 2013 9:29 AM
T
That's to create a custom bootstrapper application (BA). Easiest thing is to
use the premade or standard one with WIX: wixstba at least at first to learn.
On wixtoolset.org there is link to a book on wix and I suggest starting with
that. Also link to a manual and blogs on burn which are usefu
Hi Blair,
Issue resolved by changing the customaction to diferred and return=ignore.
Thank you very much for help.
And I have a doubt regarding CopyFile. If I use copy file element then it
copying the patch files instead of copying base file because my base files was
overiden by patch files bef
Classification: Public
I do the same thing:
So from the command line I would run MyBootstrapperEXE.exe
SERVICESLOGLEVEL=DEBUG
Now if you are just wanting to change a property via the bootstrapper you don't
have to add the variable element
Just add the MsiProperty element to your MSI:
Steve
Hi,
I am running 3 MSI from my Bootstrapper, After the first MSI is installed
successfully, I want to load an user control (Which is deployed by the
first MSI) in the bootstrapper UI. After loading the user control I will
collect some information from the user control and by clicking Next I want
to
Create a variable inside the Bundle, pass that variable to MsiProperty, and
change the variable in the bootstrapper code like
Bootstrapper.Engine.StringVariables["MyVariable"] = ""
now you can see it in the log, for the reference,
http://stackoverflow.com/questions/15305932/how-to-pass-a-property
Are you using wixstba? If so can use a wix variable LaunchTarget like this:
. This will show a launch
button on finish that the user can click.
Wes
-Original Message-
From: andreas.paetz...@btc-ag.com [mailto:andreas.paetz...@btc-ag.com]
Sent: July-19-13 6:16 AM
To: wix-users@lists.
Please read this example, this will answer all your questions.
http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/
Regards,
Rahul
On Thu, Jul 18, 2013 at 11:49 PM, Mamidi, Balasubrahmanyam <
balu.mam...@flightsafety.com> wrote:
> Thanks for reply steve. not clear
The way I accomplished this is I created a Boolean value that is true if it's
an initial install (not upgrade or uninstall), then I created an event handler
for the Finish button that launches the executable. It looks something like
this:
View.FinishButton.Click += (s, e) =>
{
Hi together,
ist there any possibility to start an application after successful bundle
installation? Already spent hours with google to find a working solution but it
seems that there isn't any...
Thanks for your help.
Kind regards,
Andreas
21 matches
Mail list logo
