Trying that again...
When I pass a variable reference such as [FOO]_[BAR] to the name
attribute of both a ServiceInstall and ServiceControl element the package
installs fine however when uninstalling the service is left running without
being stopped and removed. When I pass a literal string, the
http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern/
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Joseph L. Casale
http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern/
Much appreciated, this installer at a later must support multiple instances
at which point then this will all fit together, no need for a static location as
I assume we can compile an extension to enumerate
I get a 404 when going to http://wixtoolset.org/releases/feed/v3.10, and
the bundle can't access it either.
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in
I have been researching 'cool bobs', and while I have come to the conclusion
that this post is not directly related to the use of 'bundle of bundles', I
just had to use that acronym.
In the course of the above research I added handlers for all of the
DetectXxx and PlanXxx events to my mba. In
When I pass a variable reference to the name attribute of both a
ServiceInstall and ServiceControl
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership
Hello,
to my current knowledge, the MSI packages referenced as MsiPackage elements
within a chain must be available at build time, regardless of whether they
shall be compressed into the bootstrapper or not.
Is there a way to circumvent this? Does Burn read vital information (Product
codes
Yes, for ExePackage, not today for MsiPackage. There is a lot of information
gathered for MsiPackage that RemotePayload cannot represent. Not sure if there
is already feature request tracking it...
_
Short replies here. Complete
Custom BA could.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: RonnyS [mailto:ronnys.cod...@gmail.com]
Sent: Thursday, March 5, 2015 2:47 AM
To:
Hello,
is there some way to show in the boostrapper a message box or string in UI
due to some condition but *continue* installation?
At the moment i have this:
bal:Condition Message=#(loc.FailtureVersionNTisXP)
VersionNT v5.1
/bal:Condition
but it terminates the Installation if an user
I have a bundle (built with v3.9) with a custom managed BA with 3 packages in
the Chain- what the packages contain is not important so let's call them
PackageA, PackageB and PackageC.
I install v1 of my bundle, which installs v1 of each package.
I then start an upgrade to v2. It upgrades PackageA
Thanks, fix should be published in 15 min or so. First time we had two digits
and the redirect regex didn't expect that. Oops.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
12 matches
Mail list logo
