Based on other threads in this forum, (although I don't know that I could
find them now) I have been using Chain/@DisableSystemRestore=yes. If the
issue is related to a particular machine, you might try this and see if you
can avoid the problem.
--
View this message in context:
Use Engine.FormatString on the path (in your mba or BAFunctions.dll when
using WixStdBA, probably in the DetectComplete handler).
In mba something like this:
path =
object.Engine.FormatString(object.Engine.StringVariables[WixBundleOriginalSource])
Then save 'path' to a string variable for use in
Hello,
Thanks for the quick reply, but I don't think its what I was looking for. I
am not using any custom code for the bootstrapper or UI.
I am using the standard bundle and trying to send (as an argument) to an
executable package the source path from where the bundle originally ran.
The
I have a WiX package that should always deliver files, but should only
uninstall the files when a condition is met. The condition is that common files
should not be uninstalled if another version of the product is installed (we
are not supporting true upgrades, our upgrade is installing the
VSIX deployment is a bit tricky... but think there exist some good sources
online:
http://www.codeproject.com/Articles/838842/Deploying-snippets-within-VSIX-package
http://www.codeproject.com/Articles/873395/Installing-VSIX-package-via-WiX-installer
I have used util:ProductSearch to detect condition for my BurnPackage, but it
doesn't work, I use the last official release 3.9R2, the variable assigned is
equal to 2 (absent) even if the package is installed (I can check manually the
registry and I can find the UpgradeCode of the package in a
Hello All,
I've started working on the Wix Burn installer(on Wix 3.8) and have been loving
it so far!
I had a quick question: Is there a way to add a non-blocking condition(warning)
using the Standard BA to warn the user of any condition but not necessarily
block him from proceeding further.
wixstdba does not have support for that today.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Rajesh Nagpal (SQL) [mailto:rnag...@microsoft.com]
Sent: Tuesday, May 12,
Hi everyone,
We're struggling with a performance issue on our bootstrapper application.
Depends on the target machine (all with the same configuration), the init phase
(when Initializing... is displayed) can be quick or very, very long (up to 10
minutes !!)
This is odd, because we have another
Bundle log file would be much more telling of where the delay is.
-Original Message-
From: CALCEL Sebastien [mailto:sebastien.cal...@econocom-osiatis.com]
Sent: Tuesday, May 12, 2015 7:58 AM
To: 'wix-users@lists.sourceforge.net'
Cc: BONNET Alexandre
Subject: [WiX-users] Bootstrapper -
tucaliucmi...@gmail.com
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you
Hello Jacob,
Thanks for your reply.
Here's the bundle's log.
There is a gap of 6 minutes before the Apply begin and Creating a system
restore point.
It matches our delay duration, but it still don't have a clue about its origin.
[1E58:0ECC][2015-05-12T10:00:09]i001: Burn v3.9.1208.0, Windows
Hello,
I'm trying to use the Built-in variable WixBundleOriginalSource in order to
send to an executable package the source path from where the bundle
originally ran. This is my code
ExePackage Id=InstallConditions
SourceFile=..\Bin\$(var.Configuration)\MyPackage.exe Vital=yes
This is cross-posted from Stack Exchange
[http://stackoverflow.com/questions/30178160/use-wix-eventsource-to-create-non-localized-log].
The WiX EventSource element requires an EventMessageFile attribute. When I use
the instructions found here
#new_here. Not sure if you received this because of the spam blocker.
Hello,
I'm trying to use the Built-in variable WixBundleOriginalSource in order to
send to an executable package the source path from where the bundle
originally ran. This is my code
ExePackage Id=InstallConditions
15 matches
Mail list logo