Hello I like to use the Util CloseApplication PromtToContinue to check
whether the Internet Explorer is still open.
But i don`t like the Ignore Button on this Dialog. The using of this Button
makes me problems.
How can i remove the Button or how can i cancel the installation if the
Ignore Button
Hello,
I would like to call some executables from my Burn bootstrapper. I think that
the ExePackage element is only meant for executables brought as a payload,
not for executables already present on the target machine.
So do you also recommend to implement such a custom-action-like call in the
hi Phill Hogland, thanks for your reply and explanation about MajorUpgrade.
However are there any workaround for this situation ? and why burn unable
uninstall upgraded msi ? because based of log I have see this:
[0AB4:1B44][2015-05-20T12:33:49]i101: Detected package: DependencyA, state:
Present,
I came across a different, but I suspect it might be a related issue,
discussed in this thread
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RollbackBoundry-Can-t-Upgrade-or-uninstall-bundle-td759.html
. Frankly because of other responsibilities, I set this issue aside and
Ah, thank you. I had tried ShortName but that didn't work. I should have gone
further to just Name.
What exactly is the difference between Name, ShortName, and LongName?
Thank you,
Christoph
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Tuesday, May 19,
Phil: there's absolutely no need to apologise. All forum users (I know I am)
appreciate your input and time spent helping out on the forum.
I'll need to look into this issue anyway as part of a project of mine (which
I'll get back to soon I hope). I'll report back anything meaningful that I
In that situation, and assuming you have a robust file versioning
scheme, in all these cases you go ahaead and install the MSI anyway
and:
1. Package versions of those files that have lower file versions and
will therefore not update the existing higher versioned ones.Apply
component rules, and
See if BAfunctions in wixstdba can get you what you want. If not, would need to
create a new BA.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Tucaliuc Mihai .
IIRC, Burn should keep registration in ARP when the first non-permanent package
is installed (aka: there is something Burn would do). A RollbackBoundary after
the permanent packages *may* be necessary but my memory is fuzzy there.
_
Hello!
I need to install VC11 runtime, but specific version: 11.0.61030.0. I
implement it in this way:
util:ProductSearch
Guid=$(var.ProductGuidBsVC11)
Result=state
Variable=VC11ProductState /
PackageGroup Id=VC11PackageGroup
Hmm, turns out that MsiSetFeatureState() won’t actually install a feature if
the feature had it’s InstallLevel set to ‘0’ by the Condition table.
Now, to find out if there’s a way to set a feature’s InstallLevel through a
custom action…
On May 20, 2015, at 7:40 PM, Joel Budreau
Hey all,
I’ve got a custom action that calls MsiSetFeatureState to set a feature (that’s
initially set to InstallLevel=0 by the Condition table) to INSTALLSTATE_LOCAL.
The custom action is an immediate action that’s scheduled after CostFinalize,
but before InstallValidate.
The custom action
And it this case, how could I escape the values by hand?
I was trying to create my own Bootstraper but i cannot use .NET for it
since in production it may not be installed on every machine. Also I
downloaded the source code for wixstdba with the attempt to modify it :D
but I didn't get to far with
Historical. There was a time where you needed to track short name (for FAT)
and long name (for NTFS).
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
14 matches
Mail list logo
