The approach I use is outlined here
http://neilsleightholm.blogspot.co.uk/2012/05/wix-burn-tipstricks.html
See Signing a package at the bottom.
Neil
hello!
I'm building a Bootstrapper WiX setup system with shell scripts (not
using VS), and struggling to get the setup going completely. I hope
Hi,
Using the managed bootstrapper, I've noticed that when
the DetectRelatedBundle event gets fired, the event argument Operation is
set to MajorUpgrade, even though I only changed the version of the bundle
(and the containing MSI package is running MinorUpgrade).
I suspect this is happening
Hello, I have created a custom action in C# and can run it without
problems.
However, I would like to access the selected features in the Wix Feature
tree in the custom action to make some actions depending on that. They are
not available as properties. In the WIX file I can access them
via
Not a C# custom action expert but MsiGetFeatureState is the C++ version
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370117%28v=vs.85%29
.aspx
so it seems FeatureInfo.CurrentState and .RequestState are the equivalents.
-Original Message-
From: Hans ter Horst
You probably don't want to use TARGETDIR in this way. TARGETDIR points to the
root directorty (C:\ for example) of where your files will be installed to.
It's not typically where you put components.
See this link about TARGETDIR:
Cheers!
On Fri, Oct 26, 2012 at 1:22 PM, Peter Shirtcliffe pshirtcli...@sdl.comwrote:
Not a C# custom action expert but MsiGetFeatureState is the C++ version
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370117%28v=vs.85%29
.aspx
so it seems FeatureInfo.CurrentState and
If you also sign the MSI and include the public thumbprint of the
certificate, it's also possible to apply future patches without admin rights
(if you are patching outside of the bundle). I don't believe burn supports LUA
patching.
-Original Message-
From: Neil Sleightholm
Can the util:RegistrySearch be used in an MSI or is it burn specific?
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.commailto:n...@x2systems.com
--
The Windows 8 Center
In partnership with Sourceforge
Your
You should be able to use it in both...
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: October-26-12 12:18 PM
To: General toolset. (wix-users@lists.sourceforge.net)
Subject: [WiX-users] util:RegistrySearch
Can the util:RegistrySearch be used in an MSI or is
Hi Neil!
There is no need for the Util extension in an MSI for a registry search.
Just use the normal RegistrySearch element (from the Wix schema) which
populates MSIs RegLocator table. Because of this I think it is burn
specific.
Regards,
Georg von Kries
-Ursprüngliche Nachricht-
Von:
There is one very good reason to use it in an MSI, you can read dword values
without the # on it.
-Original Message-
From: Georg von Kries [mailto:g...@creativbox.net]
Sent: 26 October 2012 17:33
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users]
Seems to be Burn specific and sets a Burn variable while the other
RegistrySearch that's not in the UtilExtension sets a Property.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/util-RegistrySearch-tp7581620p7581624.html
Sent from the wix-users
Hello, I have a feature tree based installation, all working pretty well.
The only issue is that when I have installed a subset of features and I
want to add some more, the Change button is disabled with the mention
that there are no independently selectable features in this install. I
don't see
13 matches
Mail list logo
