Thanks for the replies.
You can use MsiSetTargetPath() in your custom action to update an existing
directory Id. That would more closely model your intent and requires less
code.
Good point, that's another option. I have been looking at what was done in
the WixQueryOsDirs custom action -
I'd just like a bit of advice/clarification on property types and CAs. If I
write a CA to fetch a folder location from the OS (to be used like
'ProgramFilesFolder') then I need to set a property (correct?) If I use a
private property I have to give it a 'default' value which is overwritten by
It looks like it might be a fairly simple extension to the OSInfo part
of WixUtilExtension/wixca. I will see if I can put something together for this.
Pete
From: peterhul...@hotmail.com
To: wix-users@lists.sourceforge.net
Date: Tue, 25 Sep 2012
I would like to use WiX to install a device metadata package. This needs to go
into a sub-folder of a folder identified by a KNOWNFOLDERID (specifically
FOLDERID_DeviceMetadataStore)
The same question was asked back in 2009 (
Date: Thu, 30 Aug 2012 18:03:02 -0400
From: mukeshj...@kpmg.com
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Major Upgrade changes requirement
What changes we need to do for Major Upgrade
Example - Product Code, Package Code, version
Thanks, that does help. If I could just ask the question slightly differently:
If I modified the WiX source, as I understand it, I would need to licence my
changed WiX source under MS-RL and make it freely available.
If I downloaded a binary of the WiX toolset and then used that toolset
From: edwin.cas...@fiserv.com
Date: Wed, 15 Aug 2012 12:12:44 -0400
I think it is important to ask these questions if only to determine the
intentions of the licensors and encourage that the license be more explicit
about its intentions. These things should not be determined in court
Date: Tue, 14 Aug 2012 21:06:07 +0100
From: br...@cran.org.uk
I'm a bit surprised that the license change wasn't highlighted - it
seems WiX is now licensed under the Ms-Rl.
I would appreciate some clarification on this license too.
(A) Reciprocal Grants- For any file you distribute that
This has been seen before and reported as a bug:
http://sourceforge.net/tracker/?func=detailaid=3431068group_id=105970atid=642714
I believe it only affects Windows XP - is that what your customer has?
I don't think there is a workaround. According to Trend's documentation, signed
executables
As I understand it, if you run the setup program from the command line with the
/log filename option you will get a log from burn and then a separate file from
the msi if it runs at all.
If I get problems I usually try to install the bare msi first and then if that
is OK I can assume it's
Dear Henning,
I think this is the same problem I have seen and reported recently to this list:
http://sourceforge.net/mailarchive/forum.php?thread_name=DUB101-W57E6E77EDBB70153F4CD0CAD7C0%40phx.gblforum_name=wix-users
I think it really is a bug (the 3.6beta worked for me) so I will file one on
OK I have filed a bug:
https://sourceforge.net/tracker/?func=detailaid=3487838group_id=105970atid=642714
I've tried to include your information, please add/correct as appropriate.
Peter
From: hkra...@infinitec.de
To: wix-users@lists.sourceforge.net
I've done a bit of playing around and it seems to be linked to install
conditions, i.e. if I change my bundle's chain to
Chain
MsiPackage Id=one SourceFile=install.msi Compressed=yes
InstallCondition= 1 /
MsiPackage Id=two SourceFile=install.msi Compressed=yes
Date: Wed, 15 Feb 2012 14:30:41 -0500
From: b...@joyofsetup.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Very simplest bundle not working
Please add that to the bug...
On 15-Feb-12 11:57, Peter Hull wrote:
I've done a bit of playing around and it seems
I've rechecked and it works fine on the beta version (build 2221 I think) - so
is this a regression or have I made a mistake in my wxs file?
I would appreciate it if someone could have a quick check of this for me. Or
should I file a bug?
Thanks,Pete
Dear All,
I've made quite a few installers and bundles with WiX already, but all of a
sudden when making a minimal example, I can't seem to get it to work! Please
can you have a look, I'm sure I must be doing something obviously wrong. This
is WiX 3.6.2603.0 on WinXP.
I've got a wxs to make
Hotmail ruined my message! Trying again..
Dear All,
I've made quite a few installers and bundles with WiX already, but all of a
sudden when making a minimal example, I can't seem to get it to work! Please
can you have a look, I'm sure I must be doing something obviously wrong. This
is WiX
The message is
0x8007051b - This security ID maynot be assigned as the owner of this object.
Here's the log:
[12B8:12F8][2012-02-06T14:21:24]: Burn v3.6.2527.0, path: C:\Users\Peter
Hull\Documents\in2it System Software\Setup.exe, cmdline: ''
[12B8:12F8][2012-02-06T14:21:25]: Setting string
thing to use is
the Package/@InstallScope attribute. Burn should automatically prompt for
elevation if it determines your MSIs are per-machine.
On Fri, Feb 3, 2012 at 12:21 AM, Peter Hull peterhul...@hotmail.com wrote:
I've made an installer for 32- and 64-bit windows with separate MSIs
I've made an installer for 32- and 64-bit windows with separate MSIs, bundled
with the standard BA (WixStandardBootstrapperApplication.RtfLicense). Both MSIs
need admin privileges and are marked per-machine. If I run the installer as a
non-admin user, the error message that the setup program
The location of the exes is taken from the registry and put in $(WixToolPath).
Can you check the InstallRoot value under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Installer XML\3.5
or
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Installer XML\3.5
and see if it is correct?
Is there any chance you could put a date and/or a changeset number by each
release so we can see easily what's new in each one?
Thanks,
Pete
--
Try before you buy = See our experts
Did you override the targets *after* Import Project=$(WixTargetsPath) /
(I'm just saying because this caught me out.)
Pete
From: scott.lang...@appsense.com
To: wix-users@lists.sourceforge.net
Date: Tue, 24 Jan 2012 10:11:19 +
Subject: Re:
If the driver is not signed, and you say it is not, then you need the Legacy
option. I did say that; what I meant was not signed with a certificate from
a CA. It is self-signed at the moment. Apologies for the confusion.
I'd still like to hear if anyone has any comments on a per-user install
From: b...@joyofsetup.com
On 13-Jan-12 01:41, Peter Hull wrote:
Bob: would it be possible to have the burn engine signed (by Microsoft) in
the released WiX 3.6
That would mean that the UAC prompt would show Microsoft as the owner of
your bundle.
OK, I had thought the UAC prompt would
I am building an installer with a device driver, to be installed with the WiX
difx extension. The driver is self-signed for testing purposes. I set my
Package element to
Package Description=...
InstallerVersion=200
InstallScope=perUser
://msdn.microsoft.com/en-us/library/ff547653(VS.85).aspx for
more info on what legacy mode is.
James
-Original Message-
From: Peter Hull [mailto:peterhul...@hotmail.com]
Sent: Monday, January 16, 2012 14:59
To: WiX Users
Subject: [WiX-users] difx extension and perMachine installs
I've used an old (2004?) version of InstallShield and it generated a setup.exe
and the msi separately. I'm assuming that setup.exe is their bootstrapper and
was well-known enough to go onto the AV makers white-lists. When burn is
released hopefully its engine could also be white-listed,
From: r...@robmensching.com
We'll need to teach this anti-virus program about Burn. Fortunately big
programs, like Visual Studio, are using Burn and if it kills them I hope we
can muster some change.
So are you saying we need to raise this as an issue with Trend Micro? Is the
program that
To sign the bundle and bundle engine you need to add the following to your
.wixproj:
Add SignOutputtrue/SignOutput to a PropertyGroup
Implement the targets like this:
Target Name=SignBundleEngine
SignFile TimestampUrl=... CertificateThumbprint=...
SigningTarget=@(SignBundleEngine) /
From: r...@robmensching.com
Date: Wed, 11 Jan 2012 07:55:13 -0800
That looks right. Please file a bug if the command-line help wasn't
helpful.
OK, bug 3472564. I've also attached a patch to the bug report - hopefully you
can use it as a starting
Signing only the bundle would prove that it came from your organisation and
hadn't been tampered with - would that be enough?
When run it would unpack the unsigned burn engine and the unsigned MSIs. Does
anyone know if that would show the user a warning (or multiple warnings?)
Bob: would it be
Date: Thu, 12 Jan 2012 20:56:15 +0100
From: n...@panorama9.com
I would start by digitally signing your burn bundle.
The bundle is already signed with a Thawte code signing certificate
The reported file name looks more like it's the extracted engine than your
bundle itself. Have you signed
Hi Nikolaj!
Could you comment on whether your installer was signed (the bundle and the
actual engine which is unpacked out of it - see this link
https://sourceforge.net/mailarchive/forum.php?thread_name=CAHdHTVc1c2h3QuYsiXWcR8A1Xtk38Z3W2KCyAvuP3hMjYqKAiA%40mail.gmail.comforum_name=wix-users
Am I right to say that the documentation for the insignia tool is a bit out of
date in the 3.6 beta?
The output from insignia /? doesn't mention the options -ab, -ib or -im.
Is the following correct usage?
- To inscribe a database installer.msi with external cabs:
1. Sign the cabs
2. insignia
Can you open a bug with this information in it? I'm not exactly sure what
we'll do about it but we should at least track the issue.
Yes I will do when I'm back in work. I am a bit surprised nobody has seen
this; I would have thought that there would be many other corporate users
with
Dear All,
I am not able to install the new 3.6 beta exe file (Wix36.exe) because my virus
checker (Trend Micro OfficeScan) terminates the installer when it tries to
write to the RunOnce registry key.
I was able to download and run WiX 3.6 from the wix36-binaries.zip archive,
however my minimal
From: r...@robmensching.com
Date: Tue, 25 Oct 2011 08:26:40 -0700
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WiX 3.6 beta and virus checker
Wow, that's a pretty aggressive virus checker. How do you install software
that requires a reboot with that thing turned on?
It's my
38 matches
Mail list logo
