Thanks, Rob.
"WixExitEarlyWithSuccess" meets the requirements.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Prevent-Downgrade-without-any-message-prompt-tp7505576p7522108.html
Sent from the wix-users mailing list archive at Nabble.com.
-
I'm having kind of the inverse problem.
Setting an "Everyone" permission to a key and all of its values, propagates
that permission upwards on the registry tree!
The following
Will set both keys: MyKey and MyRegistryFolder to have Everyone user with
The problem surfaced when I started bundling my MSI packages in order to take
advantage of bootstrapping the perquisites like .NET Framework 2.0 SP2, C++
run time libraries. We've been careful to build all of our client adapters
in .NET 2.0/VS2008 since WIN2K is still widely used in the retail worl
I remain confused how this problem has arisen in the first place. WiX
was (obviously) being compiled with versions of VS that support Win2K,
Win XP. So what's changed?
Windows XP hasn't changed under our feet. So that leaves WiX. What
features of the newer versions of Windows and/or VS are so
http://www.netmarketshare.com/operating-system-market-share.aspx?qprid=11&qp
customb=0&qptimeframe=M&qpsp=149&qpnp=11
^-- Source of my data in this message...
That is something that has been bugging me too while reading this
discussion. So my random thoughts on this topic of OS compatibility...
On 01-May-12 20:03, Bob Arnson wrote:
> See wix.chm on WIXUI_DONTVALIDATEPATH for how to skip validation.
That sounds perfect Bob. Unfortunately, now when I build from the same
source/toolset, the resulting MSI won't start at all. It gives error 1620 on
WinNT4+SP6 (but works on newer OSes). This
Hi Wix Users,
I'm trying to do what I would think would be pretty trivial and that is update
a config file value based on a parameter passed into the msi. But when I try
to do this, I keep getting the error : error CNDL0200 : The Component element
contains an unhandled extension element 'util
You want an installer designed to use instance transforms. It can be tricky
and a lot of authoring has to be done manually to make it all work, but I do
have one installer that currently supports up to 16 instance transforms.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henr
Working again with 3.6.2830.0.
Cheers all,
Palbinder Sandher
Software Platform Engineer
T:+44 (0) 141 945 8500
F:+44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Offi
Indeed you were right. There was a mismatch between the wix sources and the
wix build I had. Now everything works accordingly. Thanks again for your
help.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Customising-a-bootstrapper-theme-tp7501905p7519
Thanks again Bob.
I looked at the docs for the Product element and it is not clear to me from
this URL whether the Name property, for instance, is formatted or not:
Product Element
http://wix.sourceforge.net/manual-wix3/wix_xsd_product.htm
If you know what marks a field as formatted please let m
Hi,
I want to have multiple versions of the same product to live on the target
machine at the same time. Each of them has its own installer. To have a common
key for all versions I would like to share the upgrade code. From what I have
learned so far, the upgrade code is good for a major upgrad
12 matches
Mail list logo
