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
robmen wrote
> 1. One include the original B and C MSIs *plus* the new B and C MSPs in
> the updated Burn. Burn will only download the B and C MSIs if they are
> missing and Burn will slipstream the MSPs when possible.
This seems to work and give me the desired behavior. Thanks!
I also just foun
Thanks. AuthenticatedUser worked!
On Monday, January 6, 2014 6:14 PM, "Hoover, Jacob"
wrote:
Have you tried User="AuthenticatedUser" ?
-Original Message-
From: Goran Malovic [mailto:malov...@yahoo.com]
Sent: Monday, January 06, 2014 10:56 AM
To: General discussion about the WiX t
There are a couple options.
1. One include the original B and C MSIs *plus* the new B and C MSPs in the
updated Burn. Burn will only download the B and C MSIs if they are missing and
Burn will slipstream the MSPs when possible.
2. Make the new Bundle a patch bundle.
-Original Message-
Niel provides the infor in his blog.
http://neilsleightholm.blogspot.com/2012/05/wix-burn-tipstricks.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Chaining-NET-3-5-in-Burn-tp7591622p7591696.html
Sent from the wix-users mailing list archive a
I asked this question previously in an older, slightly unrelated thread but
I'm thinking it might be more appropriate as its own thread.
I have a bundle (lets call it Bundle 1.0) with 3 MSIs (lets say A, B, and C;
also all version 1.0).
Some of the content in B and C has changed, so I produced an
Looking at a complete verbose log may help. Otherwise there's not enough
info here to say what's wrong. It doesn't help much to say that the CA is
"something like this". For example, what type is it? We could assume it's
deferred, but it's better to know for a fact.
1. I assume the V1 install has
Hi all,
We are trying to generate a Bootstrapper Application
"CustomBootstrapperApplication" which inheritate from WixBA (which we got
from the sources of Wix 3.8).
***
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
Thanks, it is actually the file at C:\Program Files
(x86)\MSBuild\Microsoft\WiX\v3.x\wix.ca.targets that needed updated.
Brian
Brian
If you can't explain it simply, you don't understand it well enough. -
Albert Einstein
On Fri, Jan 10, 2014 at 10:51 AM, Carter Young wrote:
> Try Editing wix.
Try Editing wix.ca.targets to read
Looks like the Preprocessor Variable for $(WixToolPath) doesn't
contain the last trailing slash for the path, then submit a Bug
Request to the WiX Bugtracker and reference this Post, if and only if
the fix works.
If all goes well, the bug fix wil
Today several of our installers create a "logs" folder in a unique
location. We are planning on moving this folder to a location that is
common for all of our applications. How best should I define this
component in each of my installers? I assume I should have the same Guid
for each, right?
When I attempt to build my CustomAction project Visual Studio exits with a
code of 3.
I have tracked the issue to the way wix.ca.targets references the path to
MakeSfxCA.exe. In wix.ca.targets the following is what creates the path:
When VS 2012 uses this path it is interpreted
14 matches
Mail list logo
