Thanks to everyone for your responses. This helps a great deal and I am
most grateful. The link to the suggested post seems to confirm what
everyone is saying:
"...Took us a long time to get to a algorithm that is stable for Component
Guids. Huge win for everyone once it worked. :) – Rob Mensch
I am curious to know how WiX keeps track of GUIDSs automatically generated
for files when we use HeatDirectory.
For example, I have a project with the following in my .wixproj file...
C:\SourceControl\WiX39\
If I set AutogenerateGuids="true", my output file contains comp
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
docs that say
>> "installing feature X gives you this functionality" because it no
>> longer does.
>>
>> As Blair says, look at the verbose log. In the absence of hard
>> evidence that says what's really happening it seems premature to
>> change featur
“didn’t change”. What do your logs have to say?
Blair
From: Walter Dexter
Sent: Monday, January 27, 2014 9:53 PM
To: General discussion for Windows Installer XML toolset.
I believe that is only true for versioned files, although I may be mistaken.
In this particular case
Prefixes section) when
using the Condition type in the database (such as in the sequence tables) or
when using the MsiEvaluateCondition() function in a CA, or more directly by
using the MsiGetFeatureState() function in a CA.
Blair
From: Marek Mielcarek
Sent: Monday, January 27, 2014
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
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.
F
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
, from that file you can see that Suffix is an empty string for x86
platforms, is “_x64” for x64 platforms, is “_ia64” for ia64 platforms, and is
“_ARM” for arm platforms. ia64 was removed in v3.8. I don’t recall which
version arm was added in.
Blair
From: Martin Clarke
Sent: Saturday
API and
use it during an installation (unless you effectively make the ADK a
prerequisite). That nixes it for my use cases.
Blair
From: Phill Hogland
Sent: Friday, January 24, 2014 8:49 AM
To: General discussion for Windows Installer XML toolset.
I do not have the ADK or
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 wr
each package be
an MSI). In fact, you might even be able to reuse your current UI in a custom
bundle and save much of the redevelopment effort.
Not sure on the project leader part. What resources are available to such a
leader (types and experience of developers/testers/PMs, etc.)?
Blair
Personally I think it should have been implemented that way but it wasn’t.
Blair
From: Graham Allwood
Sent: Thursday, January 23, 2014 10:34 PM
To: General discussion for Windows Installer XML toolset.
Thanks Blair.
That did the trick.
I was trying to use element 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'
with the
bitness of the developer’s box.
var.Platform is initially set by Votive to be the value of the Platform
property (but if don’t use wixtargets it won’t be set for you) and could be
redefined just about anywhere in the build process, including in WXI files you
may include.
Blair
next time I’m faced with installers populating databases.
Blair
From: Levi Wilson
Sent: Thursday, January 23, 2014 6:37 AM
To: General discussion for Windows Installer XML toolset.
Being out of the WiX installer world for a handful of years, I was used to
writing all of
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
the service desktop on vista/2008 and newer). One of those two
will usually tell you what went wrong.
Blair
From: Palmer, Joel
Sent: Wednesday, January 22, 2014 7:14 PM
To: General discussion for Windows Installer XML toolset.
* I use WiX 3.8 to create an
MSBuild
property automatically sets the Win64 default to an appropriate value. (the
released chm docs give the wrong source for this automatic setting).
If you use the var.Platform value you are at the mercy of it being set to
something you don't expect.
Blair
From: StevenOg
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
d_Setup.log"
Adjust as needed
-Blair
From: Steven Ogilvie
Sent: Tuesday, January 21, 2014 5:29 AM
To: General discussion for Windows Installer XML toolset.
Classification: Public
We use TFS as our source repository so I get the setup source first then build
set
working solution.
Blair
From: Suvrajyoti Panda
Sent: Monday, January 20, 2014 10:51 PM
To: General discussion for Windows Installer XML toolset.
I do intend, but for that scenario i am changing the path accordingly,
using %~d0\Installers path.
On 21-01-2014 11:07
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
help us make this product better than
ever (bug reports in email tend to get lost, as this one from 2 1/2 years ago
did). And, of course, anyone can test the product in their own scenarios and
build systems and let us know how we can improve that way as well.
Blair
From: MonteChristo
pairs involving those files. Otherwise the binary table
would probably be a better bet.
Blair
From: Sean Farrow
Sent: Tuesday, January 21, 2014 1:36 AM
To: General discussion for Windows Installer XML toolset.
Hi Phil,
The compile is done at install time--after the file is copi
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.
Hi Blair,
I build them from the same machine at the same from another location
.
Blair
From: Tony Jose Mampilly
Sent: Wednesday, January 15, 2014 11:12 PM
To: General discussion for Windows Installer XML toolset.
Hi,
I have created 2 web setups in a similar manner. In installation UI, the
user can change the name of virtual directory if needed. By
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
h the bug
report.
Blair
From: Knapp Edgar
Sent: Wednesday, January 15, 2014 11:42 AM
To: General discussion for Windows Installer XML toolset.
This keeps getting returned for some reason.
-Original Message-
From: MonteChristo [mailto:edgar.kn...@sepura.com]
with MSBuild, but there are fewer of those project types remaining
with each new release of VS.
Blair
From: Dave Echols
Sent: Wednesday, January 15, 2014 10:47 AM
To: General discussion for Windows Installer XML toolset.
I have a VS 2010 solution that contains 2 Wix
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
p
view is upgraded by applying the patch).
Blair
From: Mita Patel
Sent: Tuesday, January 14, 2014 1:59 PM
To: General discussion for Windows Installer XML toolset.
Re: Deleting files in a patch.
Applying the same logic to a patch does not work.
We set the component id
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
instead of the backslash caused
your build error.
-Blair
> From: bria...@gmail.com
> Date: Fri, 10 Jan 2014 11:23:26 -0500
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Custom Action Build Error
>
> Thanks, it is actually the file at C:\Program Files
> (x
explain why explorer couldn't find the directory.
Blair
> From: simongustavs...@driveworks.co.uk
> To: wix-users@lists.sourceforge.net
> Date: Thu, 9 Jan 2014 10:13:10 +
> Subject: [WiX-users] Uninstalling with application running
>
> Good morning Wix users :)
> I&
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:
Installer to understand more. Also, there's a great book out, a
great tutorial, and lots of information accessible via Bing/Google/etc., as
well as this user list.
-Blair
> Date: Mon, 6 Jan 2014 07:48:21 -0800
> From: tr...@outlook.com
> To: wix-users@lists.sourceforge.net
> Subject
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
I honestly don't know. Maybe there's a way to format the text of each line.
Most of my projects for almost ten years now don't use MSI's UI.
-Blair
> Date: Fri, 27 Dec 2013 14:33:36 +0530
> From: dileep.sanamp...@gmail.com
> To: wix-users@lists.sourceforge.net
&g
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
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
on your log) that action must come before
SetRollbackData, which means you need that action to be After InstallInitialize
instead of before InstallFinalize.
-Blair
> From: tyler.w.r...@accenture.com
> To: wix-users@lists.sourceforge.net
> Date: Fri, 20 Dec 2013 16:30:29 +
>
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 k
directory, while not ideal, usually isn’t the end of the world. It takes
essentially no disk space, for instance, and doesn’t generally prevent
reinstallation from succeeding.
-Blair
From: Suvrajyoti Panda
Sent: Wednesday, December 18, 2013 8:40 PM
To: General discussion
dropped by the remailer, please place those files
somewhere in the cloud and provide the URL for them here in the mail list so we
can replicate your exact test case.
-Blair
From: Shyam Kannam
Sent: Wednesday, December 18, 2013 12:16 PM
To: General discussion for Windows Installer
any further.
Most of the time, files still in use can be moved (even if they are still
loaded in other processes) and the folder is thus removed during the
installation transaction (before the reboot) and the moved file is then removed
as part of the reboot sequence.
-Blair
From
reasonable to
have a feature request to have the CA overwrite whatever may have been there
before, as an opt-in thing.
-Blair
From: Graham Harwood
Sent: Monday, December 16, 2013 5:53 AM
To: General discussion for Windows Installer XML toolset.
Hi guys,
Probably a
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
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
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
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
) using the -dr
argument. You can then add your shortcuts, etc to the produced WXS.
-Blair
> From: aybe@hotmail.com
> To: wix-users@lists.sourceforge.net
> Date: Sat, 7 Dec 2013 19:29:59 +0100
> Subject: [WiX-users] Define target folder and application shortcut through
> t
dvanced Windows Installer features. Major upgrades should be your starting
point, and for the vast majority of products, will always be the superior
choice.
-Blair
> Date: Fri, 6 Dec 2013 15:49:12 -0200
> From: nicolas.alva...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subje
your project.
The tools, which are made to scale, can’t enforce what small programs need at
the expense of large programs.
-Blair
From: Phil Wilson
Sent: Thursday, December 05, 2013 8:05 AM
To: General discussion for Windows Installer XML toolset.
WorkingDirectory is
eding on setup type."
(http://www.tech-archive.net/Archive/Visio/microsoft.public.visio.developer/2006-09/msg00048.html)
-Blair
> To: wix-users@lists.sourceforge.net
> From: d...@clearskysoftware.com
> Date: Wed, 4 Dec 2013 20:30:31 -0500
> Subject: Re: [WiX-users] WiX 2.0.58
.
-Blair
From: mailc...@163.com
Sent: Wednesday, December 04, 2013 3:21 AM
To: General discussion for Windows Installer XML toolset.
Hi all，
I have a problem with wix.
There are about 3000 files in my msi and it is about 500M. When I run it at
first time, it is quickly. But if
string “bundle”). Much was
discussed this year. There are other bootstrappers that are closer to that
model.
-Blair
From: Smagin Alexander
Sent: Wednesday, December 04, 2013 3:22 AM
To: General discussion for Windows Installer XML toolset.
It was my mistake , I have tried
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
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
just one
WIXPROJ. Are you really sure you are actually in the DevBundle branch?
Simple way out: under src\packages, just open each folder and install what you
find there.
-Blair
From: Smagin Alexander
Sent: Tuesday, December 03, 2013 8:08 AM
To: General discussion for
the extremely few
cases where non-elevated code cannot read something it needs access in order to
set properties in the installation session.
-Blair
From: dileep s
Sent: Tuesday, December 03, 2013 10:46 PM
To: General discussion for Windows Installer XML toolset.
Hi All
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&#
tch file to call the tool.
-Blair
From: Smagin Alexander
Sent: Tuesday, December 03, 2013 6:31 AM
To: General discussion for Windows Installer XML toolset.
Hi people,
I want to compile wix from source code, but I didn't find any readme files "how
to comlipe wix"
msidbCustomActionTypeNoImpersonate in the Type column of the CustomAction table.
http://msdn.microsoft.com/library/aa368069.aspx
-Blair
> Date: Tue, 3 Dec 2013 07:43:08 -0500
> From: yellowjacketl...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users]
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
bundle.
Seems like everyone does it differently. Maybe we should take a poll to see if
there is any one "majority" way that we could optimize for, but even inside of
MSFT it had to be done differently for "production" signing and "internal
only-test" signing.
-Blai
@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]
"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
pplication
);
extern "C" void WINAPI BootstrapperApplicationDestroy();
and your .def file should name them the same (so they don’t get decorated) upon
export.
You return your BA class instance in the ppApplication argument, and you use
the pEngine argument to call the engine.
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 notif
forge.net
> Subject: Re: [WiX-users] [WIX]: How to trigger my MSI file when I select
> install option in Wix Custom Bootstrapper UI
>
> Hi Blair,
>
> I have created the C++ custom action project.
> Created Dialog Resource file.
> Created functions in C++ custom action DLL Main(
d, and if/when they do, to have them remove it and then repair msiNew. At
the end of the day, you will probably be telling them to do that anyway (when
they ci
rcumvent your attempts to block them from doing so).
-Blair
> From: i...@tobias-erichsen.de
> To: wix-users@lists.sourceforge.net
>
messages and the next time we triage, we may not
remember that we discussed any particular issue, especially if it wasn't added
to the issue tracker. That is how things slip through.
Jens, please enter this bug in the issue tracker on the wixtoolset.org site.
-Blair
> From: jens.teut
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
how did you load your BA?
> Date: Fri, 29 Nov 2013 11:07:37 +0530
> From: dileep.sanamp...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] [WIX]: How to trigger my MSI file when I select
> install option in Wix Custom Bootstrapper UI
>
> Hi Blai
es to
WixStdBA, because that is a BA written in C++. Another example is the WixExtBA
project on codeplex. There may be others as well (although most examples I've
seen are managed code instead of native code).
-Blair
> Date: Thu, 28 Nov 2013 12:43:53 +0530
> From: dileep.sanamp...@gma
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.s
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
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
property were it is safe.
-Blair
> From: chr...@iswix.com
> To: wix-users@lists.sourceforge.net; wix-users@lists.sourceforge.net
> Date: Tue, 26 Nov 2013 11:17:05 -0800
> Subject: Re: [WiX-users] DTF managed custom action - temporary file
>
>
>
> Here's another app
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 -080
three actions I mentioned
above.
-Blair
> From: jens.teutenb...@t-online.de
> To: wix-users@lists.sourceforge.net
> Date: Tue, 26 Nov 2013 19:54:07 +0100
> Subject: [WiX-users] DTF managed custom action - session.doAction
>
> I wrote a immediate custom action and a deferr
>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...
1 - 100 of 2073 matches
Mail list logo
