On the last step of the installation, there are texts showing:
Completed the productName Setup Wizard.
I know productName is user provide, how about other text Completed the
... Setup Wizard , are they build with the tool, or can we customize those
text ?
Thanks,
On the last step of the installation, there are texts showing:
Completed the productName Setup Wizard.
I know productName is user provide, how about other text Completed the
... Setup Wizard , are they build with the tool, or can we customize those
text ?
You can add additional text using:
Does anyone know how to change the final property page from a white
background to the default grey - so that an added check box doesn't look
ridiculous (with its grey background over the white page)?
Dave
--
Live
On 15/08/2012 09:05, David Lowndes wrote:
I know productName is user provide, how about other text Completed the
... Setup Wizard , are they build with the tool, or can we customize those
text ?
You can add additional text using:
Property Id=WIXUI_EXITDIALOGOPTIONALTEXT Value=Your
Your solution sounds perfectly reasonable.
To check compatibility in 3), youll need to have some way of discovering the
version of the addons. You could either read the addon installer's product
code in FindRelatedProducts or have the addon installer write its
ProductVersion to a
You need to supply you own version of background bitmap, see
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm. The
variable to set is WixUIDialogBmp e.g.
WixVariable Id=WixUIDialogBmp Value=Bitmaps\dlgbmp.bmp /
Neil
Does anyone know how to change the final property page from
You need to supply you own version of background bitmap, see
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm. The
variable to set is WixUIDialogBmp e.g.
WixVariable Id=WixUIDialogBmp Value=Bitmaps\dlgbmp.bmp /
Thanks Neil.
I presume the stock bitmap is just plain white?
Is
Not sure if you can make it smaller, I would try and see what happens. If
you want the originals you can find them in the source
(src\ext\UIExtension\wixlib\Bitmaps)
Neil
You need to supply you own version of background bitmap, see
I've followed the instructions here:
http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm, to
add a start menu shortcut, and while that produces no warnings, I thought it
would be more elegant to use [#MyApplicationFile] for the target like this:
DirectoryRef
Hi All,
Is there a nicer way to deliver logic that will satisfy the requirements below,
other than the attached code ?
Requirements;
a) Display specific text if releasetype (full), product(professional)
and install is not an upgrade
b) Display specific text if
I prefer to advertise my shortcuts to avoid all these problems.
On Wed, Aug 15, 2012 at 4:19 AM, David Lowndes dav...@mvps.org wrote:
I've followed the instructions here:
http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm, to
add a start menu shortcut, and while that
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
On 15/08/2012 12:55, Peter Hull wrote:
(A) Reciprocal Grants- For any file you distribute that contains code from
the software (in source code or binary format), you must provide recipients
the source code to that file along with a copy of this license, which license
will govern that file.
I prefer to advertise my shortcuts to avoid all these problems.
OK, I started down that path too and also had problems with that. :(
Do you know of a concise example of doing what I need using advertised
shortcuts?
Dave
I prefer to advertise my shortcuts to avoid all these problems.
OK, this example has sorted me out:
http://blogs.technet.com/b/alexshev/archive/2008/02/20/from-msi-to-wix-part-
10-shortcuts.aspx
It's hard to find the wheat from the chaff with all the WiX information
around. :(
Dave
Not sure if you can make it smaller, I would try and see what happens.
Nice idea, unfortunately it stretches the bitmap to fit over the whole page.
:(
Rob, would a bug report/suggestion to eliminate the background behaviour be
something that would be possible?
Dave
Working with build 2928, it seems that the burn engine adds an entry that is
visible in Programs and Features too soon.
It adds it there before anything is installed.
It can get you into some weird states.
Scenario 1: Listed in Programs and Features but not installed
There comes a point in
IIRC this worked a while ago with older WiX v3.6 builds but hasn't for a while.
If I run my Bundle with the /layout switch, it will download the .NET 4.0
Client Profile redistributable any other MSI's or MSPs I have in my bundle
which have a DownloadURL specified (and Compressed=no set).
That's the expected behaviour. The layout operation isn't meant to be an
admin install or extraction, its just to create a bundle that can be
installed without an internet connection. I think there was a thread about it
a few weeks back.
I reckon it would be a good feature request, if there isn't
My Burn package includes the .NET 4.0 client profile from WiXNetFxExtension
like so:
PackageGroupRef Id=NetFx40ClientRedist/
When I attempt to install on XP64, I get a spurious error in Burn 0x800713ec -
Asia
Log file -
WIC is definitely a prereq on Windows 2003 server so it probably is on Win xp
64 bit too. Looks like a bug to me.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Wed 8/15/2012 5:23 PM
To: General discussion for Windows Installer XML
.Net requires SP3 which x64does not have. Technically you can install it on
machines with SP2 but requires additional prereqisites. WIC is one of them.
Wes
Sent from my iPad
On 2012-08-15, at 1:29 PM, Peter Shirtcliffe pshirtcli...@sdl.com wrote:
WIC is definitely a prereq on Windows 2003
Hi everyone
I've got a Visual Studio solution that contains two WiX Projects. In Visual
Studio, I set the project properties to ignore the nearly-400 ICE30 output by
light. The WiX code was written by another programmer and I don't currently
have the time or the mandate to rewrite it so that
Bug reported -
https://sourceforge.net/tracker/?func=detailaid=3557976group_id=105970atid=642714
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 Virtual Environment**
Integrated
XP64 is a retrofitted Server 2003 x64. It has nothing to do with XP32 service
packs.
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 Virtual Environment**
Integrated Environmental
Hi everyone,
Can the WiX tools (e.g. candle, light, torch) be used within a WCF service
method? Or is there some limitation or gotcha I should be aware of? I am
wanting to answer an architectural question some of us had about the future of
my InstallerBuilder (hereafter, IB) front end. This is
I am a bit confused on the use of the InstallCondition and DetectCondition
attributes on the ExePackage element and would like some clarification on my
understanding.
Would you use InstallCondition to restrict the component being installed on
various OS configurations e.g. one package for x86
Does anyone know the best method for writing an empty Registry key under
HKCU? This code isn't cutting it:
*ComponentGroup Id=ProductComponents Directory=PersonalFolder
Component Id=CMP_RegistryWrite
Guid={3BF28DC8-4AFC-43E8-B605-AA6456B06921}
RegistryKey
Root=HKCU
28 matches
Mail list logo
