On Tue, Jan 28, 2014 at 3:39 AM, Blair Murri wrote:
> I’ve done it from a deferred DLL CA using the CreateSymbolicLink() API
> before.
>
>
> Blair
>
>
> From: Scott Palmer
> Sent: Saturday, January 25, 2014 5:32 PM
> To: General discussion for Window
e content.
>> ---
>> Phil Wilson
>>
>>
>> On Tue, Jan 28, 2014 at 5:44 AM, Walt Dexter wrote:
>> > And there's the answer. They're all in the same feature.
>> >
>> > Can I move existing files between features in an up
Are you doing a major upgrade or a recache/repair?
Are the files it was killing off in the same feature as other files that were
changed? Remember that features are installed/repaired/removed as a unit.
Your verbose install logs should be telling you why it wanted to “replace”
files that “didn
ADDLOCAL doesn’t have to be set. When costing is done in the UI sequence, the
result of that costing will be placed into the family of properties that
includes ADDLOCAL in order to communicate to the execute sequence which
features are to be changed and how (which causes things like feature
con
If your MSI package is always per-user, why wouldn’t you just retrieve and use
the path of FOLDERID_UserProgramFiles instead of ProgramFilesFolder?
Blair
From: Sascha Sertel
Sent: Monday, January 27, 2014 10:58 AM
To: General discussion for Windows Installer XML toolset.
In your conditions you probably want to use VersionNT64, not anything from the
preprocessor.
The is used to include/exclude WiX source code from your MSI/Bundle
entirely.
Blair
From: StevenOgilvie
Sent: Monday, January 27, 2014 7:27 AM
To: General discussion for Windows
http://wixtoolset.org/documentation/manual/v3/wixui/wixui_customizations.html :
Section “Inserting a custom dialog into a built-in dialog set”
Blair
From: Gustavo Martins
Sent: Monday, January 27, 2014 6:38 AM
To: General discussion for Windows Installer XML toolset.
Hi
I’ve done it from a deferred DLL CA using the CreateSymbolicLink() API before.
Blair
From: Scott Palmer
Sent: Saturday, January 25, 2014 5:32 PM
To: General discussion for Windows Installer XML toolset.
"runas" seems to be useless for installer purposes.
For one: I can'
Also all deferred actions that impersonate are different between UAC prompt and
starting from an elevated prompt (in a similar fashion). Deferred actions that
do not impersonate are identical in both scenarios.
Blair
From: Phil Wilson
Sent: Saturday, January 25, 2014 10:52
in the v3.8 wix sources: src/ext/ca/inc/caSuffix.wxi (same directory as
caSuffix.h)
That file is setup according to the way that the wix toolset itself is built,
which doesn’t always translate into how most project using votive are expected
to be built, so your version may vary.
However, fro
from: http://msdn.microsoft.com/library/windows/desktop/hh825838.aspx
“You can develop applications by using the DISM API on any computer where you
have installed the Windows® Assessment and Deployment Kit (Windows ADK).”
So, I interpret that as saying that you can’t statically link the DISM
You always control the registry key? Do it like the property remember pattern.
Blair
From: Sean Farrow
Sent: Friday, January 24, 2014 8:23 AM
To: General discussion for Windows Installer XML toolset.
Hi all,
I'm in the process of refactoring an installer I wrote a while
Certainly it is possible using a custom BA from a bundle. Somewhat less so from
an MSI. One big advantage of the bundle, however, is that the entire set of
packages can be divided up between some arbitrary set of MSIs abstracted away
from the end user (in fact, the most logical would be to have
the HarvestFile
command/element but this didn't work.
Graham
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: 24 January 2014 06:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VB6 OCX And Harvest
Add -svb6 to the
first in
Share the contents of your config file for your BA
It is probably telling the stdba that you work with 3.5 so it doesn’t run the
prereq on win7 (since 3.5 is included in win7), then the load fails because you
require 4.x.
Blair
From: sky
Sent: Thursday, January 23, 2014 10:
Add -svb6 to the
first in your WIXPROJ.
Blair
From: Graham Allwood
Sent: Wednesday, January 22, 2014 11:45 PM
To: General discussion for Windows Installer XML toolset.
Hi,
I have three VB6 components in a VB6 project I want to install and register.
Two are ocx's and
sys.BUILDARCH is the value of the -arch argument to candle, which Votive sets
to the Platform property of the project during build (so it will reflect the
build configuration, and if you build two MSIs with the same project will
probably be different values for each one). It has NOTHING to do wi
If they are not in DTF then the WiX toolset doesn’t provide them. It’s assumed
that most of what drove you to managed code would already be in the Framework
so there isn’t the same level of need to invent the wheel.
Having said that, I like John’s reply. Cool system. I’ll have to remember that
That directory does not exist on my Win8.1 box (where I have not yet installed
the ADK). So, that can’t be the runtime requirement, unless the API cannot be
used outside of generating ISOs/DVDs.
Blair
From: Phill Hogland
Sent: Thursday, January 23, 2014 6:45 AM
To: General
Windows Installer a long time ago swallowed the actual error code and
determined that this error message was the most likely cause of any failure to
install/start a service. With time that’s been proven wrong, but as Raymond
Chen would tell you about maintaining backward compatibility…
What yo
sys.BUILDARCH uses the value set via the MSBuild Platform property (x86 for
32-bit intel, etc.) automatically with recent releases of WiX. And most of the
time you don’t need to set the Win64 attribute because the same input (the
-arch argument to candle) that sets the BUILDARCH value from the M
InstallPrivileges will work, but is deprecated (or at least should have been).
InstallScope is preferred. There is no need to do both.
Blair
From: roberthyang
Sent: Wednesday, January 22, 2014 4:26 PM
To: General discussion for Windows Installer XML toolset.
Also look i
;C:\Program Files (x86)\Microsoft Visual Studio
11.0\Common7\IDE\devenv.exe" ".\Services_Setup\Services_Setup.sln" /BUILD
DebugX86 /OUT ".\Build_Setup.log"
Steve
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: January-20-14 10:53 PM
To: General discu
, Blair Murri wrote:
> And you don’t intend on installing them on any other machine?
>
>
>
>
>
>
> Blair
>
>
>
>
>
> From: Suvrajyoti Panda
> Sent: Monday, January 20, 2014 9:18 PM
> To: General discussion for Windows Installer XML toolset.
>
Please file a bug with that exact repro.
Thank you,
Blair
From: bwehking
Sent: Monday, January 20, 2014 11:50 PM
To: General discussion for Windows Installer XML toolset.
I got it!
Steps to reproduce in VS2013:
- Go to Tools->Options->Environment and choose Color theme
h-in-Certificate-element-does-not-work-td6579192.html
I suppose no one bothered to file one. I’d be happy to file the report on
http://wixtoolset.org/issues/, but what do you want me to include with the bug
report? Your message was incomplete.
Regards,
Edgar
_
From: B
http://msdn.microsoft.com/library/aa368007.aspx
“ComponentId
A string GUID unique to this component, version, and language.
Note that the letters of these GUIDs must be uppercase. Utilities such as
GUIDGEN can generate GUIDs containing lowercase letters. The lowercase letters
must be changed
.
Regards,
SuvraJyoti
On 21-01-2014 09:48, Blair Murri wrote:
> You only install MSIs on the same machine you build those MSIs from?
>
>
>
>
>
>
> Blair
>
>
>
>
>
> From: Suvrajyoti Panda
> Sent: Wednesday, January 15, 2014 11:14 PM
>
When you use the property remember pattern, all packages that store/retrieve
the property at the same location will “remember” the same value. If you need
the two setups to have different values, you should consider using two
different registry locations for your property remember pattern.
You only install MSIs on the same machine you build those MSIs from?
Blair
From: Suvrajyoti Panda
Sent: Wednesday, January 15, 2014 11:14 PM
To: General discussion for Windows Installer XML toolset.
Thanks David that works.
I have used as below:
The only certificate installation bug I found in the old sourceforge site was
this: http://sourceforge.net/p/wix/bugs/1353/ and that one was marked fixed in
2008 (it also describes a different bug with the same error code) and in the
new system is found here: http://wixtoolset.org/issues/1768/.
dunno. I always use msbuild from the command line:
“FullPathToMSBuild.exe” /nologo /t:Rebuild “FullPathToSolutionFile”
DevEnv has always been a black box and has never been particularly build-box
friendly.
You’ll have to use DevEnv on solutions containing projects that aren’t
compatible w
What is "standalonesimulator.exe"’s file id?
Blair
From: Suvrajyoti Panda
Sent: Tuesday, January 14, 2014 11:27 PM
To: General discussion for Windows Installer XML toolset.
Hi All,
I am creating an wix installer. I want to create a registry entry whose
path is not unde
Null/empty component guid components are only installed in major upgrades.
Patches are not typical major upgrades and those components are ignored (just
as with all other maintenance transactions).
As it says: it cannot be removed or repaired. A patch is basically always “a
repair” (after the
FYI: That feature request on SF now lives at http://wixtoolset.org/issues/3962/.
> Date: Fri, 10 Jan 2014 13:35:30 -0800
> From: kelly.gr...@toltech.net
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Chaining MSPs
>
> robmen wrote
> > 1. One include the original B and C MSIs *p
Most of the time if you can condition your custom actions on the action states
of some related component you will have more reliability in all use cases.
> Date: Fri, 10 Jan 2014 11:22:29 -0800
> From: phildgwil...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Custom
In both Windows Installer and in MSBuild all directory paths are always
expected to end with the trailing backslash. In fact, if you look at all of the
built-in properties for MSBuild all of the directory paths always end with the
backslash.
The fact that your WixToolPath ends in a letter inst
Depends on the file locks. A binary that is simply loaded in a process can be
moved/renamed and the directory it was originally in when it was loaded removed
without disturbing the process, but if the process is holding other files in
that same directory open with different kinds of file locks t
Please tell us how we can improve this:
http://wixtoolset.org/documentation/manual/v3/bundle/
> Date: Thu, 9 Jan 2014 00:04:47 -0800
> From: jessro...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Activation of burn step by step
>
> Need step by step directions to activ
To help avoid "prompts for source" in patch-on-patch scenarios Windows
Installer has been known to cache "originals" of files that are patched, but
that behavior can be turned off. Maybe it is off for uncompressed sources?
> Date: Wed, 8 Jan 2014 13:40:48 -0800
> From: dtkob...@gmail.com
> To:
Are your patches delta or whole file?
> Date: Wed, 8 Jan 2014 10:46:06 -0800
> From: phildgwil...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Patching compressed VS uncompressed image?
>
> It could be useful to examine the log where the patching accesses the
> netw
This speaks to the best practice of always setting up your bundles so that they
use the package hashes instead of signatures to validate that the correct
package was retrieved.
> From: dan.mad...@quanser.com
> To: wix-users@lists.sourceforge.net
> Date: Tue, 7 Jan 2014 12:22:13 -0500
> Subject:
When you have more than two possible sources for a property's value, then you
will need some intermediate properties.
Here's how that works: At the start of the sequence, a property may have been
initialized with a variable either from the property table or from the command
(or, in the case of
I assume that some file(s) that you are removing or upgrading don't extend
"Full Control" to the account named "SYSTEM", which is actually a requirement
of Windows Installer (and is the default of every single file and folder in a
fresh install of the operating system). It's possible that if
Not
PROPSERVERHOSTNAME
> Date: Thu, 2 Jan 2014 09:29:10 -0800
> From: tr...@outlook.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Unable to override SetProperty value with Edit Control
> value
>
> I have a Property called PROPSERVERHOSTNAME which I use to update an Xml Fi
ogle.com/file/d/0B-yxrdSpoNNQVEdKWnRRU1VlbmM/edit?usp=drive_web>
>
> Is it possible to display on UI using WIX controls (not BA)?
>
> If possible, please help me how to do this using WIX?
>
> Thanks in advance...
>
>
>
> On Tue, Dec 24, 2013 at 2:01 PM, Blair Murri
Extremely old documentation. This is newer:
http://wixtoolset.org/documentation/manual/v3/votive/votive_project_references.html
-Blair
> From: bria...@gmail.com
> Date: Mon, 23 Dec 2013 07:44:23 -0500
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] TargetDir question
>
> I found
Log?
> Date: Mon, 23 Dec 2013 12:34:41 +0300
> From: sergey.yuk...@visutechsystem.by
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Msi features control from own burn application.
>
> Hello.
>
> How to control features states from own burn application. I override
> OnPlanMsiFeatu
You can do whatever UI you want with a BA in a bundle, or to a certain extend
with an EmbeddedUI.
> Date: Tue, 24 Dec 2013 11:37:26 +0530
> From: wixak...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] ListView Creation
>
> Dear All,
>
> I want to create a Wix UI with L
AFAIK listviews in MSI UI can only have one column + icon.
> Date: Mon, 23 Dec 2013 14:52:11 +0530
> From: dileep.sanamp...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] [WIX]: ListView Control on WIX Custom UI
>
> Dear All,
>
> I want to create ListView control on WIX
RestoreDeprecatedFiles was scheduled right after InstallInitialize. When that
was "run" during the "immediate" or "writing the script", the
RestoreDeprecatedFiles property didn't (yet) exist (was blank), so that is what
gets passed to the CA. Later on you create the value, but it is never used.
Is this on XP or 2003, or on something newer?
> Date: Thu, 19 Dec 2013 23:53:54 -0500
> From: b...@joyofsetup.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Burn removes package it should not
>
> On 19-Dec-13 12:16, Wheeler, Blaine (DSHS/DCS) wrote:
> > I expect to see the
src/dutil/thmutil.cpp
> Date: Thu, 19 Dec 2013 14:36:30 -0800
> From: sogil...@msn.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Where in the source does it handle the image control in
> the bootstrapper?
>
> Hi guys,
>
> I am using 3.7.
>
> I am trying to figure out where
In the one component it will probably be the other RegistryValue, in the other
it will be the component's Directory
-Blair
> Date: Thu, 19 Dec 2013 13:06:06 -0800
> From: phogl...@rimage.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Adding a registry key to HKLM
>
> I d
t; Name="command_processors">
>>>> >>> Guid="{F2158D98-1DC2-4348-89FC-65A2115084B6}" KeyPath="yes">
>>>>
>>>>
>>>>
>>>> After i
You aren’t providing enough code here to verify a complete repro, and the
obvious repro from the code you do provide actually does work.
Please provide a complete example of a failing case, and please include the
associated verbose log from that same case.
Since attachments tend to be dropped
If a file being removed can’t be moved, then it will be marked for removal
during reboot, and unfortunately the folder will then be left behind (because
only file delete records are placed into the reboot sequence, not folders).
After reboot there isn’t an installation left to run to cleanup any
That’s one of those hard ones, where we don’t know if things were different
because that made them work or because someone messed them up. Most of the time
it seems that it is more likely that they were changed to make them work, so
that is what we usually err towards, but it would be perfectly
After you file the feature request, please discuss it with us on wix-devs. I’m
wondering if melt is the best place to rebase a wixpdb and I think we should
discuss the use cases and workflows before you work on the changes.
-Blair
From: Bob Arnson
Sent: Sunday, December 15, 2013
No. But directories can’t be versioned, so installation, repair and removal are
only controlled by the component’s feature(s) state and action values and
possibly the component’s own condition.
-Blair
From: uni
Sent: Thursday, December 12, 2013 9:16 PM
To: General discussio
Only with a custom action
-Blair
From: Suvrajyoti Panda
Sent: Thursday, December 12, 2013 9:51 PM
To: General discussion for Windows Installer XML toolset.
Hi All,
May be this is a trivial question to ask, but below is what i want to
achieve:
I am creating registry en
I think rebasing a wixpdb is a great feature request. If it hasn't already been
filed, please add one.
Blair
From: Tunney, Stephen
Sent: Thursday, December 12, 2013 11:57 AM
To: General discussion for Windows Installer XML toolset.
Hello all,
Ok, I finally have Pure Wi
heat dir is intended to create a relocatable component group, but not the
entire authoring. You need to tell it the identifier of the directory under
which the root of the component group will be installed (or the identifier of
the root directory if you specify suppressing the root directory) us
Don't let the name "Major Upgrade" fool you. Major upgrades are the
easiest/simplest to build/support/use way of using Windows Installer. They are
called "upgrades" because a simple command upgrades the product to the newer
version.
Minor and small upgrade/update are complex because they are i
Also large, complex programs place binaries in various different directories,
so there can be no single convention as to the “install location” nor even a
single “working directory” for those systems. As such, you are expected to
establish your own conventions and stick to them as they apply to
From: http://msdn.microsoft.com/library/aa371168.aspx the meaning of the
integer in the Root column:
The one missing enumeration represents either Machine and User, so
HKey-(localMachine|currentUser) or HKMU.
Someone else expressed it this way: "HKMU stands for either HKLM or HKCU
depeding o
You can’t skip CostFinalize, but if you don’t use the “built-in” Windows
Installer UI, you can skip the “UI sequence” (by doing your UI outside of MSI,
say in a bootstrapper).
Windows Installer is a declarative, transactional system, and it compares your
desired state against the system’s curr
which just verifies some components and
execute msi file that is placed near the setup.exe
Thanks,
Alex.
Среда, 4 декабря 2013, 9:11 UTC от Blair Murri :
>The DevBundle branch doesn’t have any of the tools that crashed for you.
>There’s no build directory created in the DevBundle branch
Just curious: MSDN says that LoadBitmap() is deprecated, and to use LoadImage()
instead. I wonder if that makes a difference with the BMP version used.
Would you mind opening a bug? I would like to test this scenario out.
-Blair
From: wdh61
Sent: Tuesday, December 03, 2013 12
Search the archives of this mail list
-Blair
From: dileep s
Sent: Wednesday, December 04, 2013 1:24 AM
To: General discussion for Windows Installer XML toolset.
Hi All,
How do I prevent the Bootstrapper.exe after triggering MSI?
Is there any solution to hide the Bootst
или один из зависимых от них
компонентов. Сбой при проверке правильности строгого
имени. (Исключение из HRESULT: 0x8013141A)
Имя файла: "DocFromXsd, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=36e4ce08b8ecfb17" ---> System.Security.SecurityExcepti
on: Сбой при проверке правильно
Windows Installer is designed to work with UAC by delaying the UAC prompt as
long as possible. There is no way to alter that without bootstrapping the MSI.
Normally that shouldn’t matter because immediate custom actions should never be
changing anything on the computer. It’s only an issue in th
I saw them yesterday as well. I’m not seeing them this morning, though.
-Blair
From: Christopher Painter
Sent: Tuesday, December 03, 2013 6:28 AM
To: General discussion for Windows Installer XML toolset., General discussion
for Windows Installer XML toolset.
I don't s
You will need to first install .Net Framework 3.5, recent versions of Visual
Studio (2010 or newer), then build and install the DevBundle branch (you can
remove the DevBundle installer if you wish, all the components it installs are
marked "permanent"). If you install multiple versions of VS, it
Deferred vs.
> elevation
>
> Thanks.
>
> What flag/option get set in Windows Installer tables when @Impersonate is
> set to 'no'?
>
>
> On Mon, Dec 2, 2013 at 11:35 PM, Blair Murri wrote:
>
> > @Impersonate='yes' is the default, so
Another way is to set the @Execute attribute of the CustomAction element to the
value firstSequence. Then you don't need to condition it nor create additional
source files.
> Date: Tue, 3 Dec 2013 13:43:22 +1100
> From: goodridge@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re
es about.
> >
> > Anyway, thanks for your help.
> >
> >
> > On 2 December 2013 17:59, Rob Mensching wrote:
> >
> > > Ditto.
> > >
> > > And if you come up with a way to set these targets by default
> > > correctly for the mu
@Impersonate='yes' is the default, so you do need to "turn off impersonation"
by explicitly saying "no".
-Blair
> Date: Mon, 2 Dec 2013 15:32:58 -0500
> From: yellowjacketl...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Deferred vs.
> elevation
>
> I have a defer
"tab a lot"?
dividing controls across dialogs is the only solution I know of...
> From: stephen.tun...@nuance.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 2 Dec 2013 17:58:15 +
> Subject: [WiX-users] UI Tricks - "Double Dialog" still required? :(
>
> Hey guys,
>
> Just got mysel
I don’t believe there’s a preference to one over the other. Each has its own
costs and risks. Whichever works better in your environment. MSBuild is
flexible in that regard. (What I do with my clients tends to vary based on the
client’s needs and customs).
-Blair
From: John Ludlow
Sen
-Blair
From: Nicolás Alvarez
Sent: Monday, December 02, 2013 9:35 AM
To: General discussion for Windows Installer XML toolset.
2013/12/2 dileep s :
> On Mon, Dec 2, 2013 at 1:21 PM, Blair Murri wrote:
>> I was referring to the code in SampleDLL.dll. I assume you a
Was your command prompt elevated? Do you need to make your custom action
deferred with impersonation turned off?
-Blair
> Date: Mon, 2 Dec 2013 19:53:13 +0530
> From: suvrajyo...@contata.co.in
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Fwd: Getting error notification when run
that burn install actions.
>
>
>
> Thanks in advance.
>
>
>
>
> On Sun, Dec 1, 2013 at 2:43 PM, Blair Murri wrote:
>
> > how did you load your BA?
> >
> > > Date: Fri, 29 Nov 2013 11:07:37 +0530
> > > From: dileep.sanamp...@gma
If msiOld has no guard at all, then it will potentially install itself on "top"
of anything, no matter what you do. All you can do is reduce its vectors of
installation.
If someone presents your msiOld via MSI double-click, you can prevent its
installation by having another MSI with the sam
Bugs discussed on these lists remain on these lists unless tracked, and the
only way it will be tracked is if someone enters the bug into the tracking
system. The best person to enter an issue into the tracking system is the
person that discovers the bug, not necessarily the person who proclaims
Do "msiBlock" and "msiOld" share the same ProductCode?
Is that ProductCode (or any ProductCode) also shared by "msiNew"?
Do all three share the same UpgradeCode?
Does "msiOld" have any code to guard against it being the source of a downgrade?
> From: i...@tobias-erichsen.de
> To: wix-users@lists.
When Burn installs a newer MSI that MSI should still generally remove older
versions of itself (#1 reason: your customers may not do what you expect).
Having said that, if an MSI does what is expected, then the older MSI will be
removed as part of its upgrade. When the older bundle is then remo
"alternately":
http://wixtoolset.org/documentation/manual/v3/msbuild/daily_builds.html
> Date: Fri, 29 Nov 2013 14:25:22 +1100
> From: goodridge@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Cannot create patch using 3.7/3.8 when original MSI
> built with 3.5
>
Only via using the technique documented here:
http://wixtoolset.org/documentation/manual/v3/msbuild/daily_builds.html
> From: steven.ogil...@titus.com
> To: wix-users@lists.sourceforge.net
> Date: Thu, 28 Nov 2013 16:48:26 +
> Subject: Re: [WiX-users] WiX v3.8 released! [P]
>
> Classificati
r,
>
> Thank you for the information..
>
> Can you give some example to call the BootStrapper Install action using
> PFN_BOOTSTRAPPER_APPLICATION_CREATE method .
>
> Please help me...
>
> Thanks in advance
>
>
>
> On Thu, N
When your PFN_BOOTSTRAPPER_APPLICATION_CREATE method (prototyped in the
IBootstrapperApplication.h file) was called that you used to create your UI,
you were passed an IBootstrapperEngine pointer. You call the engine methods
directly on that interface pointer (which is defined in the
IBootstrap
I don't recognize it but a Bing search turned up this page:
http://portals.altiris.com/portals/13/sdk/smp%207.0/SolutionDev/UnderstandingAndCreatingInstallationsUsingWIX.html
-Blair
> Date: Thu, 28 Nov 2013 11:12:21 +0530
> From: subrat.w...@gmail.com
> To: wix-users@lists.sourceforge.net
> Su
The -arch command-line argument is what sets the default value of @Win64 on
things like the RegistrySearch and Component elements, not the
Package/@Platform attribute.
That is a doc bug. Please file it so we get it corrected.
-Blair
> Date: Wed, 27 Nov 2013 19:46:10 +0200
> From: igor@g
ack-y way to do it, either way i found the bug
> report http://sourceforge.net/p/wix/bugs/3163/ so hopefully will be fixed
> soon :) Thanks
>
>
> On Tue, Nov 26, 2013 at 1:53 PM, Blair Murri wrote:
>
> > The CustomAction tag inside of the UtilExtension for the deferre
That is certainly a reasonably good way to transfer structured data. I believe
the concern was one of space, but if you compressed the json (which already has
a low overhead and compresses well with algorithms that are good with text) you
may fit the entire table into the CustomActionData proper
You could also put the actual path into the CustomActionData. Realize that
anything that the nonelevated immediate action has write access to isn't secure
and could be tampered with before the elevated deferred access can access it.
-Blair
> Date: Tue, 26 Nov 2013 11:06:00 -0800
> From: phild
Between InstallInitialize and InstallFinalize all deferred actions are written
into the installation script (along with the properties named after them at the
same moment in time). When any of the InstallExecute, InstallExecuteAgain, and
InstallFinalize actions run, they run the script from wher
>From what I can see poking around the "*" should not have been dropped...
> Date: Mon, 25 Nov 2013 13:57:26 -0500
> From: yellowjacketl...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] WiX 3.7: iis:WebAddress IP="*" works,but generates
> different .config entries...
The CustomAction tag inside of the UtilExtension for the deferred portion of
the XmlFile custom action doesn't have the HideTarget attribute set. I thought
there was an issue opened on that at some point, but I don't recall right now.
You could update the MSI post-binding to set that bit in the
You call Detect, then Plan, and then Apply on the engine. How you intersperse
those calls with what you show when in your UI is ultimately up to you.
> Date: Tue, 26 Nov 2013 11:55:54 +0530
> From: dileep.sanamp...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] [WIX]: How
1 - 100 of 537 matches
Mail list logo
