I also tried using util:FileSearch giving it the path of one of the files
this msi installs but turns out that the Path attribute doesn't takes an
absolute path(complains of ':' in the Path). My source code for building
this setup bundle lies in a different drive than the drive where this file
gets
Hi Phill,
The event has already been wired up in the Class constructor. I just missed to
copy the code in the email.
But my problem is even after registering the event in the constructor it
doesn't work.
Thanks & Regards,
Mohit
-Original Message-
From: Phill Hogland [mailto:phogl...@
Hello All,
I'm trying to "detect" where a particular msi is installed or not and based
on that I want to block on my burn setup bundle.
I tried looking for a registry entry installed by that msi and doing a
util:RegistrySearch but I need one more piece of information on what version
of that msi i
>From what I have read, this is related to where RemoveExistingProducts is
scheduled (probably using MajorUpdate/@Schedule).
This link provides details on when the old uninstallation will be
rolledback.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.
With great respect for Rob, and I agree that bal:Condition does not support a
non-blocking warning today, however by adding a BAFunctions.dll to your
StdWixBa bundle, you can implement c++ code to detect different conditions,
and then use the information to log, display a string on a dialog, or blo
Nope, sorry we still have these 6 min of initialization.
-Message d'origine-
De : CALCEL Sebastien [mailto:sebastien.cal...@econocom-osiatis.com]
Envoyé : mercredi 13 mai 2015 14:07
À : 'General discussion about the WiX toolset.'
Objet : Re: [WiX-users] Bootstrapper - Initializing phase v
An example of doing this is in the wix source at:
src\Setup\WixBA\InstallationViewModel.cs
The event is registered in the class constructor (along with some other
event which are helpful):
WixBA.Model.Bootstrapper.Error += this.ExecuteError;
And then the ExecuteError handler has an example of
Thnaks for your reply Phil.
We'll try this.
-Message d'origine-
De : Phill Hogland [mailto:phogl...@rimage.com]
Envoyé : mardi 12 mai 2015 19:00
À : wix-users@lists.sourceforge.net
Objet : Re: [WiX-users] Bootstrapper - Initializing phase very long
Based on other threads in this forum, (
Hi All,
I'm using a custom bootstrapper and I'd like to display a custom error message
or log the error if one of my MSI fail.
I tried using the BootstrapperApplication.Error event to handle the error, but
in case of error from MSI this below piece of code is never called.
private void OnError
Make a bundle:
http://robmensching.com/blog/posts/2012/6/25/b-is-for-bundle-and-thats-good-enough-for-me/
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Gareth Price [mail
10 matches
Mail list logo
