http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012(v=vs.85).aspx
Symbol names and values are case sensitive.
Environment variable names are not case sensitive.
Literal text must be enclosed between quotation marks ("text").
Note Literal text containing quotation marks cannot be used
Digitally sign the original MSI, include the public cert in the
MsiPatchCertificate table, and then sign the MSP with the same certificate.
And in the wixproj,
http://timestamp.digicert.com /a "%(SignCabs.FullPath)"" />
http://timestamp.digicert.com /a "%(Si
I assume your bundle is a per-user bundle with a per-machine prereq. If so,
set ExePackage/@PerMachine = yes.
-Original Message-
From: Marco Tognacci [mailto:mark...@live.it]
Sent: Tuesday, June 25, 2013 12:20 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Burn setup set pr
The A msi was successfully upgraded though. The issue is there are 2 installer
transactions that are run in sequence. The first works, the second fails.
It gets difficult to roll back the bundle, because it would need to reinstall
the previous bundle if the upgrade failed. What if the original
Burn "can" cache them, but if you set *Package/@Cache to 'no' it won't.
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: Wednesday, June 26, 2013 12:05 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Bootstrapper multiple MSI’s don’t rollback to a
I would check to see that the machines are up to date with Windows updates,
specifically looking for the root certificate updates.
-Original Message-
From: Wheeler, Blaine (DSHS/DCS) [mailto:bwhee...@dshs.wa.gov]
Sent: Wednesday, June 26, 2013 3:15 PM
To: 'General discussion for Windows
beginning to roll out Win 7 and I have to
support XP thru at least the middle of next year. This isn't a show stopper
but it is annoying.
-----Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Wednesday, June 26, 2013 1:27 PM
To: General discussion for
riginal Message-----
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Wednesday, June 26, 2013 4:39 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn bug or at least a puzzle
If you go to a failing box and right click on the signed exe, select
pr
This would get ugly if you had mixed bundles with other installers (Exe
packages from 3rd parties).
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Thursday, June 27, 2013 12:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users]
I think the intent would be to have a "Preqba.wxl". Have multiple files with
the same name in LCID specific sub folders.
So,
http://example.com/license.html";
LogoFile="path\to\customlogo.png"
/>
...
I know 2 is by design. If a user selects uninstall from ARP, then they
shouldn't go into maintenance mode with an option to repair/etc. I don't use
the GAC so I can't comment on 1.
-Original Message-
From: Lu, Jie (Ruth) [mailto:ruth...@intergraph.com]
Sent: Thursday, June 27, 2013 1:1
What would be really handy is a ba/ux with a feature tree selection driving
multiple msi packages. This would need to be in addition to WixStdBA, but
"getting it right" and doing it in a reusable way isn't a trivial task.
Handling upgrades would be especially tricky as a bundle can't currently
Why not localize the Burn bundle? Can you not utilize one MSI with component
conditions based on language (assuming you have language specific files to
deploy)? Are you trying to show the MSI's UI?
Depending on what your MST changes, you might be able to utilize
SystemLanguageID - gets the la
I would concur with Blair. I also seem to remember the reasoning behind this
was older supported operating systems (XP) didn't have an API to get the
"friendly" names. (Ex: GetUserDefaultLangID vs GetUserDefaultLocaleName)
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Se
The MST doesn't have to be embedded, it's just "easier" to do it that way. You
could just as easily have them external, and instead of
Value=":[TransformFileName].mst" use Value="[TransformFileName].mst". Then you
would need a http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multip
Do you still have the computer management console open when doing the uninstall
(but after stopping the service)? I seem to remember bugs in the snap in that
either leaked handles or maintained an exclusive lock on the SCM that would
exhibit this behavior.
-Original Message-
From: Alain
I have not personally localized a bundle. The hints and pointers I am giving
you are based off of the current Wix codebase. Wix has had several generations
of developers and the documentation is less than perfect. (It's open source,
so anyone is welcome to contribute more documentation / how
Sounds like you need to write your own UX/BA. You shouldn't depend on a CA
"securing" an install, as there are several tools out there that would make it
easy to modify and remove said check. You could base your UX off of WixStdBA
(C++), or you could write a managed one (.Net). If you clone t
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-Wix-3-5-Heat-Cannot-harvest-64-Bit-COM-DLL-Registry-Data-td7583833.html
http://sourceforge.net/p/wix/feature-requests/399/
The first is a reference to someone having a possible solution, the second is a
link to the feature request
I think I was having similar issues, and I reverted to using
http://wix.sourceforge.net/manual-wix3/patch_building.htm It does have some
shortcomings
(http://blogs.msdn.com/b/heaths/archive/2010/08/24/comparison-of-patchwiz-and-wix-v3-patch-build.aspx
) , but it allowed me to create patches o
1) yes
2) you could
3) yes, you could but you would need to manually extract the dll in you managed
ca (after embedding it in the msi) and then pinvoke that dll. Fairly certain
.net requires the native libs to exist as its loading your assembly, so you
would need to build the reference to the n
I haven't tried this yet, but it looks like you could just pass the additional
DLL's name to MakeSfxCA.exe to include additional files with your CA.
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Tuesday, July 02, 2013 2:13 AM
To: General discussion for Windows Insta
You might want to have a read over at
http://stackoverflow.com/questions/14814014/msi-multi-instance-installation-with-patches.
Multi-Instance installs are tricky enough to get right, adding the patching
on top of it can become real confusing rather quickly. Other than that, there
isn't much w
First guess is you have = and/or ; inside of your INI file contents. If you
are using DTF/Managed CA, I could see this potentially causing issues. You
might want to try manually parsing the Session [CustomActionData.PropertyName]
and see if you have better luck.
-Original Message-
Fro
the problem. To my knowledge I am not including this file explicitly
in my code. I am unsure how it is grabbing the content of my .wxl file and
sticking it in this file. Is this by design or is it indicative of a flaw in
my code?
From: Hoover, Jacob [via Windows Installer XML (WiX) tools
included a line
similar to the red one, so I tried that as well but they both produce the error.
From: Hoover, Jacob [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+s687559n7587087...@n2.nabble.com]
Sent: Tuesday, July 02, 2013 11:43 AM
To: Mark Van Dyke
Subject: Re: Burn - Localizati
r error, however, it then does not grab the correct localization
file. It is still showing the English localization values.
From: Hoover, Jacob [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+s687559n7587094...@n2.nabble.com]
Sent: Tuesday, July 02, 2013 2:23 PM
To: Mark Van Dy
dentifiers Duplicated
Yes they do. Those 3 localization files in those 3 subfolders contain the
correct mbapreq.wxl files. The mbapreq.wxl file in the root folder contains
the 1033 values. But my region is set to French (Canada) on the target install
system.
From: Hoover, Jacob [via Windows Installe
You could create a new MSI and bundle with a higher version number but with the
older files. As long as you schedule remove existing products "early" in the
chain, it will remove the bad build before installing the fixed/reverted files.
-Original Message-
From: jo...@msli.com [mailto:jo
Burn and its existing WixStdBA don't support this out of the box today. I see
two choices for you. The first is to have a single msi with no transforms and
either use multiple components with conditions on the localized shortcuts or
utilize a CA at runtime to inject the localized shortcuts into
I've been signing a msi and its external cabs without issue.
Can you provide the steps you are using to see if I can spot anything?
On Jul 8, 2013, at 9:30 AM, "Georg von Kries" wrote:
> Hi all,
>
>
>
> I've been using a element in our installers for several
> years now, just in case we wan
elf if this is an bug or if I did something
wrong.
Thanks for your help,
Georg
-Ursprüngliche Nachricht-
Von: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Gesendet: Montag, 8. Juli 2013 16:38
An: General discussion for Windows Installer XML toolset.
Cc: wix-users@lists.sourceforge.net
Betreff:
he MSI IMHO.
>
> It is currently not an issue for me, as I have no plans to use patches
> in the near future. But I was asking myself if this is an bug or if I
> did something wrong.
>
> Thanks for your help,
> Georg
>
>
> -Ursprüngliche Nachricht-
>
Did you look at my previous suggestion
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-shortcut-localizations-in-one-MSI-td3437236.html
? (I know they didn't have conditions, but it appears as if they had a
functional work around.)
-Original Message-
From: TimM [m
Hmm, are you sure that is going to work? If the product code is the same for
all of them, I am betting the upgrade/repair scenario isn't going to work as
expected. (If the install condition is false, but it detects the product is
installed...)
-Original Message-
From: TimM [mailto:timm
I don't believe Windows installer would support this, even if it did one could
use orca to bypass it. If it were me I would use burn and a custom ux/ba.
On Jul 10, 2013, at 8:02 PM, "Raghu" wrote:
> Hello WIX Experts,
>
> The following is my scenario:
>
> On a UI Dialog, I have an edit co
You don't/can't. Before elaborating, if you want to install a service then why
not use the ServiceInstall/ServiceControl elements which exist today? Getting
code right which modifies machine state is hard to do, as you have to handle
the install/upgrade/repair/remove operations along with roll
erties from it. I had seen the Handle method but was
sure there was a way to pass a value to my CA parameters. I'll change my
approach to the problem and use the handle as suggested.
Thanks
Marc
-Original Message-----
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent:
The answer is "kind of". IE, you don't need it installed to use it (assuming
you don't need the Visual Studio integration). Take a look in the help docs
(in 3.7, look for the topic " Integrating WiX Projects Into Daily Builds").
-Original Message-
From: keith.doug...@statcan.gc.ca [mai
léphone 613-951-4405 Facsimile |
Télécopieur 613-951-1966 Government of Canada | Gouvernement du Canada
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: July-11-13 12:56 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
Take a look at the InstallSize attribute of your *Package elements in the
bundle. InstallSize = The size this package will take on disk in bytes after
it is installed. By default, the binder will calculate the install size by
scanning the package (File table for MSIs, Payloads for EXEs) and us
You need to reference the component/componentgroup from within a feature in
order for Wix to include it.
-Original Message-
From: Richard Silverstein [mailto:rsilverst...@conarc.com]
Sent: Friday, July 12, 2013 1:04 PM
To: General discussion for Windows
Jacob. But I'm not sure where this code piece goes.
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Friday, July 12, 2013 2:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] help needed including directories
You ne
>From http://msdn.microsoft.com/library/aa371634.aspx, it appears to be
>possible (Name = This column is the string naming the service. This column can
>be used to control a service that is not installed. ). Have you tried adding
>a ServiceControl element in the same component that contains you
+1 for don't do it. Have the application modified to write to "proper
locations".
http://msdn.microsoft.com/en-us/library/windows/desktop/bb762494(v=vs.85).aspx
commonly CSIDL_COMMON_APPDATA with \Mfg\App Name appended.
-Original Message-
From: Edwin Castro [mailto:egca...@gmail.com]
A bundle with two msi packages ...
Sent from my iPhone
On Jul 17, 2013, at 11:08 AM, "Wheeler, Blaine (DSHS/DCS)"
wrote:
> You can't do that.
>
> -Original Message-
> From: Parkes, Kevin [mailto:kevin.par...@wacom.eu]
> Sent: Wednesday, July 17, 2013 9:02 AM
> To: wix-users@lists.s
Why wouldn't you want burn if you need a bootstrapper? Did you install Wix, or
are you using the zip of binaries? How are you building your bundle (command
line or via Visual Studio)? What version of MSBuild or VS are you using?
-Original Message-
From: José Marques [mailto:jose.marq.
ate 2012.
I've found very little information about the error I'm getting (see my first
post), and that's why I'm struggling with burn.
Thank you very much for all the replies.
On Thu, Jul 18, 2013 at 3:44 PM, Hoover, Jacob
wrote:
> Why wouldn't you want burn if you nee
One option would be to use an immediate custom action that copies the existing
files to the temp folder, and then a semi-custom action which copies those
files to your "backup folder".
-Original Message-
From: Srinu ..., [mailto:srinu_...@yahoo.com]
Sent: Friday, July 19, 2013 9:29 AM
T
Are you doing a native or managed BA/UX? Is this "control" a native or managed
control?
If it's a native UX/BA and the control is a COM component, you should be able
to create the object after it's installed. If it's managed, you would have to
do some rather involved coding to delay load the a
the below example.
http://bryanpjohnston.com/2012/09/28/custom-wix-managed-
bootstrapper-application/
Thanks!
Regards,
Rahul
On Fri, Jul 19, 2013 at 7:40 PM, Hoover, Jacob
wrote:
> Are you doing a native or managed BA/UX? Is this "control" a native
> or managed control?
>
&g
The bundle and installer logs would tell the story... Start with the bundle
log and ensure it is passing the default value to the MSI, then inspect the MSI
log file to find where the property is changing.
-Original Message-
From: Freedman, Mark P. [mailto:mark.freed...@jhuapl.edu]
Sent
I personally prefer my CA's to be in C++, and if you so choose you could use
some of the functionality in dutil. Ex: FileVersionFromString,
FileVersionFromStringEx in fileutil.
-Original Message-
From: Phil Wilson [mailto:phil.wil...@mvps.org]
Sent: Tuesday, July 23, 2013 3:06 PM
To:
If you could get the logs posted I am sure a few others would take a look at
them as well. If you don't have your own hosting, you could use tools like
SkyDrive or DropBox to share the logs.
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: Tuesday, July 23, 2013 3:30
That's not a proper link, click on the Share Link option in drop box and it
will give you a URL (with a bunch of random or checksum based info in it). Ex:
https://www.dropbox.com/s/jcr5mu6q8rqwrg9/...
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: Tuesday, July 23
Wix/Burn doesn't have a service portion written so it's dependent on Windows
Installer constraints. If there is a need to update without admin privileges,
either an Administrator must push the updates via a tool like SCCM/AD/etc, or
the install/app would need to be reworked as a per-user applica
Again,
If the install is Per-Machine then Burn is going to request elevation. The
only way to avoid this is to make it a per-user install or have an
administrator deploy the updates.
One could write a service which is going to be ran as admin (to service the
update), however this opens up a
Burn is prompting for credentials.
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: Wednesday, July 24, 2013 10:51 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] prompt for administrator account during major upgrade
[P
Tim,
Wixtoolset.org has a link to the bug tracker.
As for localizing, you would need to create a WXL file for the bundle. When
you include it in the payload via a Payload element, I believe they all need
the same file name but should be located in LCID specific sub folders. As for
the nam
That's where you use burn to install these "other softwares".
-Original Message-
From: Chaitanya Sanapala [PC-BLR-DEV] [mailto:chaita...@pointcross.com]
Sent: Thursday, July 25, 2013 8:30 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom action [
Since Wix is open source and community driven, I am sure someone will make it
work with VS2013 once it is RTM. A beta/preview is open for things to change,
so I doubt anyone would have undergone the effort as of yet.
-Original Message-
From: Ivanoff, Alex [mailto:alex.ivan...@shavlik.co
Is your DLL project output set to register for COM interop? Are you building
your install as part of the solution containing the source projects? Have you
ensured your assembly is not registered prior to building the installer project?
Have you tried to manually run heat against the release fold
Ok, regfree won't work for you. By chance do any of the other binaries refer to
your shell extension?
You should be able to unregister the one in the debug folder by using regasm.
On Jul 27, 2013, at 12:45 PM, "Marco Tognacci" wrote:
> I need to register this dll for registering a shell exten
You might not be able to use the MajorUpgrade element (I haven't tested this),
but if you author your Upgrade/UpgradeVersion elements to find and remove it
you shouldn't have issues. The only down side is if they try to rerun the bad
install after upgrading then that install won't be able to de
I think the part you are missing is " all changed components from that fragment
will show up in your patch". I can't imagine only wanting a patch to contain a
subset of changed components.
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Monday, July 29, 2013 1
Is the folder there after a reboot?
Sent from my iPhone
On Jul 31, 2013, at 11:16 AM, "Blair Murri" wrote:
> What does the log say?
> Most often it is that a file was held by something (usually anti-virus) but
> released before the transaction finished (the file was thus deleted by the
> time
That "should" work, remembering you need both a 32bit and a 64 bit MSI. Though
I do think you have the MergRef's inverted based on the condition...
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Wednesday, July 31, 2013 11:48 AM
To: General discussion for Windows I
om
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Wednesday, July 31, 2013 12:22 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in
Product.wxs [P]
That "should&q
ent lib\x86
and lib\x64
steve
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: July-31-13 2:56 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need help, how to put a condition on a merge module in
Product.w
Make sure you are signing your bundle using the provided targets. If unsure,
post what you are using.
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Tuesday, August 06, 2013 4:29 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Burn 'Unspecified Err
+1 for fixing your source msi an recaching the msi. I wouldn't recommend
modifying the cached version, especially if this bug made it into the wild.
On Aug 28, 2013, at 11:18 AM, "Simon Gerhold" wrote:
> Thanks, good to know :)
>
> Simon Gerhold, razvojni inženir / Development Engineer
> Ceti
Personally,
If this file may or may not be there, I would use a "Semi-Custom" Action to
inject a temporary record into the MoveFile table. You may be able to get the
same action done without a custom action, but then I would question if this
file should be considered user modified and thus not
You could clone his branch and do your own build. The turnaround time for
getting it out on an official build will require a ticket/triage, translation
consideration, review and blessing from Bob (and possibly other things I am
forgetting). Even if it was out on wixtoolset.org, it would be a
You need a separate property for the search, and a CA to assign a value to the
VS12_ROOT_FOLDER if it exists.
IE:
...
VS12_ROOT
...
I believe the mantra is don't use installer UI's, use a BA UI. As such, if
you need a custom UI then generate a BA to give the look and feel that you
want. The reasoning behind having a BA UI is so you can have a single unified
installation experience. Having a chain of 5 MSI's all exposing
WixStdBA "should" be able to show those messages (in 3.8).
Since I didn't want to change existing behavior, if you get a copy of the
RtfTheme.xml file, and insert
Into the
section, and then include the custom theme in your bundle via
You should get what you are looking for.
You could write a custom BA, but if your "script" is going to modify machine
state then it doesn't belong in the BA.
Is there a reason you can do this in a custom action? Even if you don't own
either MSI, you could create a 3rd MSI to put between them which simply deploys
the changes in ques
2013 support is on the list, but hasn't been completed.
-Original Message-
From: Albert van Peppen [mailto:alb...@insad.nl]
Sent: Wednesday, September 25, 2013 10:43 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] [SPAM] Re: Weekly releases
Mainly
Installer XML toolset.
Subject: Re: [WiX-users] [SPAM] Re: Weekly releases
Do you have an ETA for VS 2013 support?
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Wednesday, September 25, 2013 10:46
To: General discussion for Windows Installer XML toolset
Wasn't there a bug a while back where the ACL's on the package cache were
getting messed up and causing similar behaviors? What version of Wix is your
installer using?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Thursday, September 26, 2013 11:03 AM
To:
Normally you would need multiple wxl files all included in the same bundle.
http://stackoverflow.com/questions/11250597/creating-localized-wix-3-6-bootstrappers
Assuming you are using WixStdBA, the engine will probe for a lcid specific file
before going for the one in the root.
-Original M
As Chris outlined in in his answer, If you want an Install time variation point
you'll have to go the mutually exclusive component route or the harder
dynamically emmited ServiceInstall table route using custom actions that
leverage SQL Temporary Tables. ( Much harder... )
The first involves de
Reboot, since it's 100% effective.
In a multi-user environment, you wouldn't want to be killing everyone's shell
off (if it were even possible). If it were me, I wouldn't force the reboot
either. (Similar to how TortoiseGit upgrades happen; I can ignore the reboot
till it suits me.)
-Origi
How is it crashing? Are you using a custom BA or WixStdBA? Do you have a
reproducible test case?
The BA certainly shouldn't crash.
-Original Message-
From: rowbot [mailto:james.row...@microfocus.com]
Sent: Monday, October 07, 2013 10:20 AM
To: wix-users@lists.sourceforge.net
Subject:
If it were me, I'd add something like...
< IsTfsBuildAgent Condition=" '$( IsTfsBuildAgent)' == ''">no
...
$(DefineConstants);
IsTfsBuildAgent =$(IsTfsBuildAgent);
To your WixProj. Then you should be able to do:
Better yet, you could use SourcePath as a MSBui
Or install to a common location this file, and utilize the CopyFile element to
stick it in the destination based on bitness. I'm not 100% certain, but is it
not possible to have both X86 and X64 versions of powershell on the same system?
-Original Message-
From: Steven Ogilvie [mailto:st
Merryweather Cooper
Build & Install Engineer -- ESA
Jack Henry & Associates, Inc.(r)
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Tuesday, Octobe
2858: The data for the bitmap [2] is not valid.
I'd assume it's the older OS's which are having issues. Odds are you are using
something in the image (Alpha channel / transparency) or a format that that OS
doesn't support. You could try a different format. From the MSI SDK, the Bitmap
control
Or ditch the MSI UI and write a BA/MBA and be able to do whatever you want.
-Original Message-
From: Christopher Painter [mailto:chr...@iswix.com]
Sent: Wednesday, October 09, 2013 2:03 PM
To: General discussion for Windows Installer XML toolset.; General discussion
for Windows Installer
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 Custom
Would be interesting to see if the parent PID is really burn starting another
burn instance, or if the CA inside the MSI that is running about that time is
spawning it (process explorer would tell you this). I also think were missing
a log file for the second instance of the bundle that spawned
What's incredibly strange is that it's MsiExec that is spawning the installer.
As such, I'm wondering what is inside the Wise installers CA that fires right
before the second instance spawns.
-Original Message-
From: Alexey Larsky-RUS [mailto:alexey.lar...@jeppesen.com]
Sent: Monday, O
46C_00600810A1CE did not close 1
MSIHANDLEs.
Internal Error 2769.
FixComponentConditions.DC957364_DE35_11D3_B46C_00600810A1CE, 1
What I did notice is even your Quiet install shows this mystery instance being
spawned.
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenhec
The engine is going to have "burn.related.upgrade" passed as a command line
option, but as that is an internal burn parameter it won't get passed to your
BA. The engine does set pCommand->relationType = BOOTSTRAPPER_RELATION_UPGRADE;
Take a look at Command.Relation.
-Original Message-
Since your property is camel case it won't be passed from the InstallUISequence
to the InstallExecuteSequence. In addition to that you will need to set the
Property/@Secure to yes to allow the engine to pass it's value.
In this case, I would think you would need a new property that you define a
SHA-1: 2414f339da083a2ffaa52fe4f26868e4fe8205e0
* Merge branch 'bugs_3839_4093.2' of
https://git01.codeplex.com/forks/bobarnso/wixdev into wix38
SHA-1: da66059ce782a8b3563bc53798e8affb17ba74f9
* Fix WIXBUG:3839 and WIXBUG:4093.
* Add projects to build version-specific templates for VS2012 an
Did you remember to increment the version of the bundle? Is it the bundle that
is left behind in ARP?
-Original Message-
From: Robert Nell [mailto:robe...@eosgroup.com]
Sent: Monday, October 21, 2013 6:03 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bootstrapper ARP cleanu
You can just attribute the appropriate File as a KeyFile (See File/@KeyPath).
-Original Message-
From: Hans ter Horst [mailto:hoshis...@gmail.com]
Sent: Tuesday, October 22, 2013 8:55 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Something I noticed with Servic
http://robmensching.com/blog/posts/2012/8/20/the-wix-toolset-license
https://wix.codeplex.com/license
I'm not a lawyer, but the intent of the license is such that if you modify the
Wix source you need to contribute it. Building installers from Wix doesn't
have any impact for commercial product
Take a look at CustomActrion/@HideTarget
-Original Message-
From: Tunney, Stephen [mailto:stephen.tun...@nuance.com]
Sent: Wednesday, October 23, 2013 12:25 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Hiding CustomActionData values in MSI logs
Hello
1 - 100 of 740 matches
Mail list logo
