Mike Dimmick wrote:
Having downloaded the latest
weekly (3.0.2128.0), I can confirm that this seems to work - setting
-dWixUILicenseRtf=License.rtf caused it to be picked up and used in the
MSI.
Yes, the idea is to be more flexible than the WiX v2 approach. Using
WiX variables is m
Rob Mensching wrote:
> So does that mean you are writing it, Bob?
>
I'll happily put it on my ever-growing list. Maybe even in the top 10,
as I think this would be a very useful CA. But that still puts it
somewhere in 2009.
--
sig://boB
http://bobs.org
---
Arnette, Bill wrote:
RE: [WiX-users] Installing machine-specific license files
Actually, I was thinking I could use the same
product code, upgrade code, and component ids for each customized
license file installer. I don't think this will be a problem. Am I
missing something?
You can’t do that. I suggest reading the documentation
that Jason pointed out. It explains how limited exe CustomActions can
be. If you really want that much control over your installation, you
should write a DLL CustomAction. Those have the ability to be more
robust.
From: [
Thanks, Jason. I looked up
the information in the link but couldn’t find anything that would be
helpful to me.
Suppose I want write an
installer wix file that executes app.exe sometime during installation. If
app.exe returns 0 it proceeds with the installation, if it returns 1, it
op
When using Return="check", the executable should return zero for success and non-zero for failure. I don't think there is a way to respond to different returns - if it fails, your install halts. If it succeeds, the install continues. If you need to pass information back from the executable, cons
Hi,
I’m still new to Wix, so I’m sorry if my
question may seem rudimentary to you.
I’m trying to get Wix to execute an application that
returns a status (i.e. OK or an error code), and have Wix checked on the return
status and perform further action based on the returned status. I
Why are you running heat.exe each time you
build? I would think you just run it once, and then modify the source
files to fit into your build environment.
I was able to get heat working with DLLs
that had a dependency on MSVCR80.dll with a heat.exe.manifest that contains the
following:
Thanks for the info Mike. I think it
has more to do with the manifests in the DLLs and lack of manifests in some.
If I remove a manifest from a DLL that has one of the VC80.CRT dependencies
then I will get more of these pop ups. I know that I have 34 DLLs that
have VC80.CRT dependencies
Dear Albert Tuulas,
Look at LsaAddAccountRights/LsaRemoveAccountRights WinAPI functions.
--
Best regards,
Valery mailto:[EMAIL PROTECTED]
-
Take Surveys. Earn Cash. Influence the Future of IT
Jo
Having downloaded the latest weekly (3.0.2128.0), I can
confirm that this seems to work - setting -dWixUILicenseRtf=License.rtf caused
it to be picked up and used in the MSI.
--
Mike Dimmick
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
DimmickSent: 29 September 20
It looks like you need to add
-dWixUILicenseRtf= to the light command line to
change this variable. Right now I can't validate this as I have the 3.0.2015.0
version installed and I can't build the SampleUI tutorial (gets LGHT0132 errors
complaining that nothing's a valid assembly, even thoug
Thanks Stefan,
I'm going to use IE, as my browser now and may be try to use default
browser later.
Thanks anyway
Leila
-Original Message-
From: Stefan Pavlik [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 28, 2006 11:52 PM
To: Leila Lali (Excell Data Corporation)
Cc: Bob Arnson; Wi
One other thing I would check for - make sure you don't
have a custom action which is overriding what you specified from the
command line. That bit me one time! :-)
Regards,
Richard
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matthew
JanulewiczSent: Thursday, September
So does that mean you are writing it, Bob?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Thursday, September 28, 2006 18:49
To: Wilson, Phil
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Launching a CHM
Wilson, Phil wr
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Thursday, September 28, 2006 18:49
To: Wilson, Phil
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Launching a CHM
Wilson, Phil wrote:
> If Wix actually
> has a built-in cu
I am trying to customise the standard Wix UI by including
our own licence file and branded backgrounds.
I can not seem to be able to work out where to put my files
in order to get them picked up. I am using Wix version 3 and are happily building
using the WixUIExtension. But all the exa
Hi Bob,
been there. I find that something similar is done with WinDbg.
Thanks to all for helping out. Keep you posted.
Best regards,
Calin
Bob Arnson wrote:
> Calin Iaru wrote:
>> I see that MigrateFeatureStates discovers that the features are
>> installed. Next, InstallValidate says t
18 matches
Mail list logo