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 - t
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
t
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 09:27
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 (
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Instal
> 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, vers
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
(unchang
> 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 cour
> Date: Wed, 15 Aug 2012 13:08:06 +0100
> From: br...@cran.org.uk
> This sounds to me rather similar to requirement iv. under the previous CPL:
>
> iv. states that source code for the Program is available from such
> Contributor, and informs licensees how t
> 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=detail&aid=3431068&group_id=105970&atid=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
executabl
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 somet
.Pete
> 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
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
it works, even with these 'silly' conditions.
> Date: Wed, 15 Feb 2012 10:43:09 -0500
> Fr
OK I have filed a bug:
https://sourceforge.net/tracker/?func=detail&aid=3487838&group_id=105970&atid=642714
I've tried to include your information, please add/correct as appropriate.
Peter
> From: hkra...@infinitec.de
> To: wix-users@lists.sourceforge.net
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.gbl&forum_name=wix-users
I think it really is a bug (the 3.6beta worked for me) so I will file one on
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
>
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 3.6
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 a
er
>
>
> 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, cmdl
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-06T
rn should automatically prompt for
> elevation if it determines your MSIs are per-machine.
>
> On Fri, Feb 3, 2012 at 12:21 AM, Peter Hull wrote:
>
> >
> > I've made an installer for 32- and 64-bit windows with separate MSIs,
> > bundled with the standard BA
>
Just to confirm, I have finally got my Code-Signing cert and, with everything
signed it still triggers Trend (on Windows XP, seems OK on Windows 7). I'm
going to make a minimal installer and send it off to our IT department,
hopefully they can ask Trend to investigate.
Has anyone else made an
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 gi
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?
Otherwi
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 in
Did you override the targets *after*
(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: [WiX-users] When install exe built wi
> 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 inst
quot;, configures DIFxApp to install
> unsigned driver packages and driver packages with missing files"
>
> Also see http://msdn.microsoft.com/en-us/library/ff547653(VS.85).aspx for
> more info on what legacy mode is.
>
> James
>
> -Original Message-
> From
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
element to
and everything seemed fine. However I reasoned that a device driver had better
be perMachine so I changed the InstallScope to per
> 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 ha
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, assumin
> 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
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
> 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 p
To sign the bundle and bundle engine you need to add the following to your
.wixproj:
Add true to a PropertyGroup
Implement the targets like this:
You need to put these _after_ the
Alternatively you can use for more
control.
There is also a target but I
> 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 tha
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 -i
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.com&forum_name=wix-users
> > 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
> wi
> 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?
I
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
41 matches
Mail list logo
