Look at WixBA.cs line 147 and it (I think) does what you are wanting to do
after the install in the mba right before the BA exists.
this.PostTelemetry();
this.Engine.Quit(WixBA.Model.Result);
You would probably want to change the 'Telemetry' code to create a http post
that
Thanks! it works!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-CustomAction-in-WPF-Bootstrapper-application-tp7589611p7589618.html
Sent from the wix-users mailing list archive at Nabble.com.
---
___
From: ZivCizer [cize...@gmail.com]
Sent: Thursday, October 10, 2013 5:12 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using CustomAction in WPF Bootstrapper application
Thanks Tom,
So, as i understand, in my case, i should use the BA just to support the UI,
and all other actions as
Use a property, and configure the bundle to pass the engine variable to the
MSI. (See MsiProperty in the docs.)
-Original Message-
From: ZivCizer [mailto:cize...@gmail.com]
Sent: Thursday, October 10, 2013 9:13 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using
Thanks Tom,
So, as i understand, in my case, i should use the BA just to support the UI,
and all other actions as the one i mentioned should be implemented as
CustomAction as one of the "InstallExecuteSequence".
When trying to do so, i encountered this problem:
I have a textbox in my window that
CustomAction belongs to MSI not to BA
I don't think it is a good idea to change machine state in the BA
Tomer Dror
Intergraph Corporation.
Intergraph Israel.
P: +972 (4) 8779191-1222
Skype:tomer.dee
http://www.intergraph.com
.
From: ZivCizer [ci
I think you need "do_install" to come after InstallFiles, otherwise the file
won't be installed. Also, didn't look close before, but you need your
CustomAction to be deferred so that it happens during the script execution
phase instead of the script generation phase.
-Original Message-
Well, this is my install-sequence:
NOT Installed AND NOT
REMOVE
Installed AND NOT
REMOVE
Installed AND
REMOVE
Hmm, if it's actually that hard to do, I'll probably stick with installing my
files to some "dummy"-location - even though it will never be used exc
When are you executing the CustomAction?
PS: if you don't want to install the file, then you'll need to either write a
block of code to temporarily extract it to disk (lots of work to get that right
in all cases securly) or try to find it on source media (lots of problems if
the source media i
Thanx for the hint, but somehow that doesn't quite work as expected ... maybe I
should post some of my wix-code ... maybe I'm doing some stupid wrong ...
--- cut --- cut--- cut--- cut ---
--- cut --- cut--- cut--- cut ---
I don't want to "install" the wsp-file somewhere on my ma
The Formatted topic in the MSI SDK describes the magical syntax to get you the
full path to your file: "[!FileId]". Lots of other good stuff in that
particular help topic.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Henning Eiben
Sent: Monday, April
ember 18, 2007 9:25 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using CustomAction during the installUISequence
Sorry, i m attaching the installation log:
Hope that helps
Rob Hamflett wrote:
>
> 'ends prematurely' isn't much to go on. Does it repor
Sorry, i m attaching the installation log:
Hope that helps
Rob Hamflett wrote:
>
> 'ends prematurely' isn't much to go on. Does it report error numbers?
> Does a logged installation
> report anything useful?
>
> Rob
>
> chandan Koushik wrote:
>> Hi All,
>> I have a config.cpp file which co
'ends prematurely' isn't much to go on. Does it report error numbers? Does a
logged installation
report anything useful?
Rob
chandan Koushik wrote:
> Hi All,
> I have a config.cpp file which contains the function
>
> _declspec(dllexport) UINT CheckBluePrint (MSIHANDLE hInstall)
> {
>
14 matches
Mail list logo
