I have an installer that uses Burn. If I rebuild the installer without
changing any content and then run that installer it will install another
version alongside an existing one?
Using the individual MSI installers there is no issue with upgrades. This only
occurs when running the burn
Hi Experts,
My second day using WiX and I ran into this challenge. I have a bunch of
html,css and js files (200+) organized in nested folder structure.
Is it possible to use wix for packaging these files and then run this setup
on another machine to install the same folder structure and files?
hi,
I created a default ui for my changes,i need to merge the ui with
wixui_installdir
how is to possible,
thanks regards,
Chaitanya.
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
Hi,
I found some ways to use the value inserted in a input control:
- I can set a property with the input value;
- I can use the publish tag to perform actions such as a setproperty
making use of the inserted value;
I have a couple of questions:
- Is the publish tag the only way to perform
hi,
I need to read an Apache Software installed path from Registry.i need to
update that path in my main registry
Any suggestions Acceptable.
Thanks Regrds,
chaitanya.
--
This SF.net email is sponsored by Windows:
http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou
rce-file/
-Original Message-
From: Subbiah Ganesan [mailto:subbiahtv...@gmail.com]
Sent: 13 June 2013 06:47
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix help
Use wix
I usually received this message on windows server 2003 when the windows imaging
component is missing...
-Ursprüngliche Nachricht-
Von: Rob Mensching [mailto:r...@robmensching.com]
Gesendet: Mittwoch, 12. Juni 2013 16:19
An: General discussion for Windows Installer XML toolset.
Betreff:
It appear there's a bug in WiX 3.8 that causes the bootstrapper not to
restart installation after a reboot (at least on Server 2003 x64) if
variables are specified on the command line. For example if I run:
ProductNameSetup.exe /passive
The the system will reboot and installation will
Hi all,
I am trying to hide the options button on my bundle install as the install
folder is fixed and cannot be changed. I am having trouble getting the
SuppressOptionUI=yes to work.
I am using WiX 3.7 and here is my bundle.wxs from my VS2010 solution. Any help
would be greatly appreciated.
Classification: Public
Try this:
BootstrapperApplicationRef
Id=WixExtendedBootstrapperApplication.HyperlinkLicense
bal:WixExtendedBootstrapperApplication
SuppressRepair=yes
SuppressOptionsUI=yes
LicenseUrl=
/bal:WixExtendedBootstrapperApplication
Thanks Steve,
When I try and build that though I get
The BootstrapperApplicationRef element contains an unexpected child element
'bal:WixExtendedBootstrapperApplication'.
Dave Moss
Tactical Team Lead
OmPrompt
+44 (0)1235 436014 Direct
davidm...@omprompt.com
www.omprompt.com
OmPrompt Limited
Classification: Public
Oops using an extended bootstrapper extension my bad, see change:
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.HyperlinkLicense
bal:WixStandardBootstrapperApplication
SuppressRepair=yes
SuppressOptionsUI=yes
LicenseUrl=
Yes. All but one of my installers supports a web-based WCF service. One of
these services also deploys a significant amount of HTML, jScript, and CSS.
Payload is payload.
--
John Merryweather Cooper
Build Install Engineer - ESA
Jack Henry Associates, Inc.®
Shawnee Mission, KS 66227
Hi Steve,
Changed to the updated version and I am now getting The
BootstrapperApplicationRef element contains an unhandled extension element
'bal:WixStandardBootstrapperApplication'. Please ensure that the extension for
elements in the 'http://schemas.microsoft.com/wix/BalExtension' namespace
Hey,thats great news.i kept looking the internet but found nothing that
could help.can you please point me to any tutorials.thanks in advance.
Nitin
On 13-Jun-2013 7:05 PM, John Cooper jocoo...@jackhenry.com wrote:
Yes. All but one of my installers supports a web-based WCF service. One
of
Classification: Public
Dave
Go back to your original code and just modify it to look similar to this:
BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.HyperlinkLicense
bal:WixStandardBootstrapperApplication
SuppressRepair=yes
SuppressOptionsUI=yes
Go here: http://www.wixtoolset.org/
Under documentation there is a book you can buy and/or a link to a tutorial.
When I started I got the book. Trying to do it without is painful. The
tutorial is pretty good as well.
-Original Message-
From: Nitin Sharma
I need some help finding a good behavior for uninstalling using bundles.
My bundle installs 4 things (wxs at end of this message):
Two ExePackage,
Two MsiPackage
From Control Panel-Programs and Features,
I see an entry for each item in my chain, which I like.
I also see multiple entries for
I am starting to wonder if the way I am trying to use Burn might be the issue.
I am trying to provide a single installer that will install that includes a
32bit and a 64bit MSI and will install the correct version. There are no
related packages.
Nik Twerdochlib
Software Developer
You need to increment the version of the bundle every time you build it (and
deploy it). Also, what is the intent behind the RelatedBundle elements? Having
a bundle related to itself and set to upgrade just seems wrong to me.
-Original Message-
From: Nik Twerdochlib
You need something like this example of RegistrySearch that sets a property:
http://wix.sourceforge.net/manual-wix3/read_a_registry_entry.htm
You'll need a custom action to read that property, add your data creating
another propertyb that you can then write to the registry with a
RegistryValue
I following online instructions and created a patch (msp file). There were no
errors during the creation. When I tried to verify the patch by applying it, I
got following error:
MSI (s) (C0:F0) [13:36:29:463]: Executing op: ActionStart(Name=CreateUser,,)
MSI (s) (C0:F0) [13:36:29:463]:
22 matches
Mail list logo