G20
0SP
Email Disclaimer
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 23 April 2012 11:46
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to false,
attempts minor upgrade
Furt
Upgraded from WiX v3.6.2816 to v3.6.2823. Haven't changed anything in source.
MSI's build fine but my burn bundle fails now. Log is as follows:
-- Rebuild All started: Project: VESetup, Configuration: Release x86 --
Deleting file "obj\Release\Bundle.wixobj".
r upgrade
Sounds like we should scan patches for those that disallow removal and mark
them permanent.
The InstallCondition behavior is expected. If the InstallCondition is false
that means "this Package should not be Installed" (aka: should not exist on
the box).
On Wed, Apr 25, 2012 at
[06A0:0B6C][2012-04-26T14:56:20]: Burn v3.6.2816.0, Windows v6.1 (Build 7601:
Service Pack 1), path: C:\ProgramData\Package
Cache\{c4017423-730a-47fe-b473-eec0fa8071db}\ve2012setup.exe, cmdline:
'/uninstall -burn.unelevated BurnPipe.{07CEB968-F392-4BE0-A3CF-F00525E5A2C7}
{50F4EFE9-76A5-
upgrade
kicks in.
On Thu, Apr 26, 2012 at 3:11 AM, Pally Sandher wrote:
> I've removed the InstallCondition for the patch & it's now working as
> intended. Thanks for the input on this however I would point out the
> documentation mentions nothing about "patch ap
quot;slipstream" MSPs and Burn
will be able to install the original MSI and the MSP in one transaction if
the MSI isn't present already and only install the MSP if the MSI is
already installed. It's really cool.
On Thu, Apr 26, 2012 at 8:06 AM, Pally Sandher wrote:
> Not too bo
t see the Reinstall in the log file. It looks like the ve2012.msi is
being uninstalled and there was a user cancel.
On Thu, Apr 26, 2012 at 7:56 AM, Pally Sandher wrote:
>SourceFile="..\..\..\install\ve2012.msi"
> After="SharedC
utting edge is named incredibly appropriately.
On Thu, Apr 26, 2012 at 2:44 PM, Rob Mensching wrote:
> I don't see the Reinstall in the log file. It looks like the ve2012.msi is
> being uninstalled and there was a user cancel.
>
>
> On Thu, Apr 26, 2012 at 7:56 AM, Pally
http://wix.tramontana.co.hu/tutorial/user-interface/new-link-in-the-chain
That should get you started.
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 Solution
9:30 AM, Bob Arnson wrote:
>
>> On 25-Apr-12 11:45, Pally Sandher wrote:
>> > Microsoft (R) Windows Installer Xml Linker version
>> 3.6.2823.0
>> > Copyright (C) Microsoft Corporation. All rights reserved.
>> >
e) evaluation that installs the
baseline+MSP in one transaction if the baseline is not on the machine (aka:
nothing installed or older version installed) or installs only the MSP if
the basline is already on the machine.
Using slipstreaming is a 300-level concept in Burn that definitely needs
documentat
cotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20
0SP
Email Disclaimer
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 27 April 2012 16:07
To: General discussion for Windows Installer XML toolset.
Subject: Re
release (3.6.2823)
On 30-Apr-12 11:10, Pally Sandher wrote:
> Unfortunately still happens with 3.6.2328.0.
Heath's fix came in v3.6.2830.0.
--
sig://boB
http://joyofsetup.com/
--
Live Security Virtual Co
When WiX was hosted on SourceForge there were handy RSS feeds for the daily
builds along with change lists e.g.
http://wix.sourceforge.net/releases/wix3.6.feed
Sadly since the move to codeplex/wixtoolset.org these no longer exist (or I
can't find them). Could we get these brought back as it was
X 3.6 weekly build release notes/changes
I asked something similar recently and I don't believe this is available yet.
As a workaround I download the source and look at the history.txt file.
Neil
-Original Message-----
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 08 May 201
Are you sure you have RemoveExistingProducts scheduled?
Sounds to me like when you install the later version, it's incrementing the
Component Reference count which is why uninstalling the old one works fine (all
it does is decrement the Component Reference counts) & would explain why the
direct
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20
0SP
Email Disclaimer
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 25 April 2012 14:58
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn feedback
tions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20
0SP
Email Disclaimer
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 09 May 2012 06:23
To: General discussion for Windows Installer XM
Nice, thanks Rob =)
I may have just missed this on the web page as I switched to Chrome recently
which doesn't have any built-in RSS detection like Internet Explorer (I now
have an extension installed to do this though).
Cheers,
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945
Upgraded to v3.6.2914.0 from v3.6.2907.0. None of my MSI projects build anymore
(7 in the same solution, all fail but my one wixlib in the solution still
builds).
light.exe(0,0): error LGHT0001: Cannot set column 'Value' with a null value
because this is a required field.
Except
ICE errors aren't WiX errors.
Here's your hint as requested ->
http://msdn.microsoft.com/en-us/library/windows/desktop/aa369206.aspx or if
that's not enough how about
http://msdn.microsoft.com/en-us/library/windows/desktop/aa369022.aspx
I think what you may be missing is basic troubleshooting
According to
http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm you should
just need to set the WIXUI_EXITDIALOGOPTIONALCHECKBOXTEXT property to an empty
value for the checkbox to not show. WiX v3.5 sources also show similar. How you
do that is up to you. Type 51 Custom Action
34 AM, Pally Sandher wrote:
> Upgraded to v3.6.2914.0 from v3.6.2907.0. None of my MSI projects build
> anymore (7 in the same solution, all fail but my one wixlib in the solution
> still builds).
>
> light.exe(0,0): error LGHT0001: Cannot set column 'Value' with a
rge.net
Subject: Re: [WiX-users] MSI projects fail to build after upgrading to
v3.6.2914.0
On 15-May-12 06:34, Pally Sandher wrote:
> at
> Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase(Output output, String
> databaseFile) in e:\delivery\Dev\wix36_public\src
ubject: Re: [WiX-users] MSI projects fail to build after upgrading to
v3.6.2914.0
On 15-May-12 10:53, Pally Sandher wrote:
> Done ->
> https://sourceforge.net/tracker/?func=detail&aid=3526942&group_id=105970&atid=642714
Thanks. Fixed for Monday's build. I am curious, h
; E aaron.oxf...@objecttrading.com
> T +61 2 9450 2999
> F +61 2 9245 2744
> W www.objecttrading.com
> This message may contain privileged and confidential information
> intended only for the use of the addressee(s) named above. If you are
> not the intended recipient of
1 - Slipstreaming MSP's doesn't work
Code:
[snip]
[snip]
What's meant to happen:
On a machine which has an existing v2.0 or later MSI installation, the MSP
should be applied to update to v2.2
On a machine which has nothing installed, v2.2 should be insta
You need to harvest the DLL as well as the TypeLib.
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
Regis
Run heat.exe on the DLL *as well* not *just* the TypeLib.
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
Does your DLL expose the DLLRegisterServer function? If so are all its
dependencies available to heat when you're trying to harvest it? Both are easy
enough to check using dependency walker.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www
Is your MSI per-machine or per-user?
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 Office -
Kelly I saw those same errors a while back which were caused by our AV
(Symantec Endpoint Protection v12) heuristic detection blocking Burn from
extracting stuff from itself when it was unsigned. We reported it to Symantec
but other AV products may have similar issues.
Have you tried signing you
http://wix.sourceforge.net/manual-wix3/heat.htm
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
Registere
Sounds like either as Rob says an API call which doesn't exist on XP or a
missing dependency (essentially the same thing).
Open your DLL in dependency walker on XP & see what it says.
Once you get it registering manually, use heat to register it the proper way in
your MSI.
Palbinder Sandher
Sof
P
Email Disclaimer
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 23 May 2012 20:33
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Issues with Burn (WiX v3.6.2921.0)
On 22-May-12 08:22, Pally Sandher wrote:
> 1 - Slipstreaming MSP's doesn't w
Also it'd be much less convoluted to show your custom dialog before the
VerifyReadyDlg rather than after and make more a lot more sense to configure
the installer before the user clicks install rather than after.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 1
tell) and see if we can get the customer to try again.
Pally: We are signing the bundle, the bundle engine, and the MSI file.
Hopefully that should take care of any problems with AV.
Kelly
On May 24, 2012, at 3:38 AM, Pally Sandher wrote:
> Kelly I saw those same errors a while b
If you're not using auto-generated Product & Package GUIDs, you'll need to
manually change them every time if you want to use Major Upgrades.
Package GUIDs should be auto-generated regardless. Product GUIDs are dependent
on your patching policy (in a nutshell keep it the same if you want to use M
Use the Windows Installer UI instead of a Custom Action showing a MessageBox?
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 S
ce - Helix Building, West Of Scotland Science Park, Glasgow G20
0SP
Email Disclaimer
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 29 May 2012 03:32
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Issues with Burn (WiX v3.6.2921.0)
On 22-May-12 08:22, P
Nope. Use a Bundle to sequence your installers.
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
Registere
http://wix.sourceforge.net/manual-wix3/run_program_after_install.htm
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 N
.NET 4.0 doesn't exist on Win 7/Server 2008 R2. It has to be installed.
http://wix.sourceforge.net/manual-wix3/wixnetfxextension.htm
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 **
In
The WiX Tutorial should help you get started -> http://wix.tramontana.co.hu/
It's far superior to the help files for learning the basics.
Also you can't send attachments to the list, they get stripped by the
sourceforge list-bot. Better to paste your code into your message.
Palbinder Sandher
S
Also you can display RTF files in Windows installer using the RichText control
as per the LicenseAgreementDlg in WiX_UI.
Might be a simpler/more elegant solution than having a button launch the RTF.
Any reason why you need the RTF to be in the Binary table rather than part of
the install?
Palb
Which is why I recommended you start with the tutorial rather than wade in knee
deep with the reference docs.
Have you looked at it yet?
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 **
Another workaround is to make the size of the checkbox control only as large as
the box itself so there's no grey background visible & use a separate text
control which can be set to have a transparent background. Breaks screen reader
compatibility though if you're willing to live with that.
Pa
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).
Howe
eature request, if there isn't one already, to
have an extract switch for the scenario you suggest.
-----Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Wed 8/15/2012 4:04 PM
To: General discussion for Windows Installer XML
toolset.(wix-users@lists.sourcef
My Burn package includes the .NET 4.0 client profile from WiXNetFxExtension
like so:
When I attempt to install on XP64, I get a spurious error in Burn "0x800713ec -
Asia"
Log file ->
http://upload.iesve.com/downloads/burn_issues/xp64_net4clientprofile.log
Burn screenshot ->
http://upl
ion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn - .NET 4.0 client profile fails to install
onWindows XP 64-bit
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 [ma
them.
Wes
Sent from my iPad
On 2012-08-15, at 1:29 PM, "Peter Shirtcliffe" wrote:
> 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:pal
novate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20
0SP
Email Disclaimer
-Original Message-----
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 15 Augus
Try using the "Suppress specific warnings" field in the individual wixproj
files where appropriate.
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 L
Alternatively use the merge modules & save yourself the hassle of having to
update your code every time there's a security update for Visual Studio.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate
Works fine for me. Have you modified the Burn UI? When an MSI is cancelled, the
"cancel" button becomes a "close" button for me.
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 **
Integra
LocalAppDataFolder is perfectly acceptable. The ICE38 error is telling you that
you need to change the KeyPath for your components to be compliant with Windows
Installer expected behaviour.
It sounds to me like you've written a per-machine package & are trying to turn
it into a per-user package
I wouldn't recommend circumventing Windows Installer practices just because you
refuse to do things the correct way.
As Rob said it's explained how to work with per-user components in
http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm
Palbinder Sandher
Software Platform Engin
Upgrade to v3.6 not v3.5 as it's already had at release candidate status & will
be officially released pretty soon. You can then use Burn to bootstrap the .NET
4.0 framework as part of your install process.
As far as I remember it's a straight upgrade from v3.0 to v3.5 or v3.6, should
be no chan
Sounds like your Component GUIDs are different & thus you've broken the
Component Rules ->
http://robmensching.com/blog/posts/2003/10/18/Component-Rules-101
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate +
For all those like myself whom have been updating regularly with the latest WiX
v3.6 builds, the release is version 3.6.3303.0 while the last weekly release
build was 3.6.3227.0 so you probably want to update one last time.
The RSS feed doesn't list 3.6.3303.0 (as yet) so like myself, you may not
This is what you're doing wrong ->
http://msdn.microsoft.com/en-us/library/windows/desktop/bb204770.aspx#concurrent_installs
This is how you fix it ->
http://wix.sourceforge.net/manual-wix3/authoring_bundle_intro.htm
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44
To start you off see
http://neilsleightholm.blogspot.co.uk/2008/08/customised-uis-for-wix.html
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 Limite
I've had to quote this to co-workers enough over the last 6 years that it
should probably be tattooed on my forehead at this point
See
http://msdn.microsoft.com/en-us/library/windows/desktop/aa511445.aspx#elevationgl
specifically the section titled "To eliminate unnecessary elevation:"
also see
You need to target Windows Installer 5.0 (which means Windows 7 and later only
I'm afraid) ->
http://msdn.microsoft.com/en-us/library/windows/desktop/dd407936.aspx
Example code on Bob A's blog ->
http://www.joyofsetup.com/2009/01/17/msi-v50-features-in-wix-v30/
Palbinder Sandher
Software Plat
Why aren't you simply using
...
As per the manual at
http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/install_dotnet.html
?
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.ies
Other than increasing the size of your binaries I don't see much of an issue.
Why do you need CString specifically?
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 Environmen
What happens if you run your installer without .NET 3.5 installed? Does it
exhibit the same behaviour on all the versions of Windows you expect it to be
run on?
Which version of the .NET framework are your custom action projects targeted
at? (in Visual Studio right click the project -> Properti
Anyone seen this before? I've bundles built using WiX v3.6 which are failing to
apply a patch which has been signed by a renewed code signing certificate. The
bundle was signed by the previous certificate which expired last month but both
the bundle & the patch show up as valid signatures when I
ccess and the proper
certificates aren't on the computer.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: April-01-14 9:33 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bundle fails to verify signature of payload
Anyone seen this before?
I'll give that a try but it doesn't help for existing Bundles & I don't
particularly want to rebuild dozens of released Bundles just to fix this.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate wit
BRB, doing that on every machine across the planet.
This just in, WiX error codes != Microsoft error codes.
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 Sol
ws Update uses the MSI
Installer as the main method of distribution, so I tend to disagree in
this case.
Carter
Quoting Pally Sandher :
> BRB, doing that on every machine across the planet.
>
> This just in, WiX error codes != Microsoft error codes.
>
> Palbinder Sandher
> So
Unless you also change the Upgrade table when you're poking around in your MSI
with Orca, it's not going to see the "2.0.0.0" as a new package if you didn't
add a MajorUpgrade element when you authored your package.
See
http://wixtoolset.org/documentation/manual/v3/howtos/updates/major_upgrade.
http://wixtoolset.org/documentation/manual/v3/wixui/dialog_reference/wixui_installdir.html
Palbinder Sandher
Software Platform Engineer
T: +44 (0)141 945 8500
F: +44 (0)141 945 8501
http://www.iesve.com
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registe
http://wixtoolset.org/documentation/manual/v3/xsd/wix/customaction.html
See the 'Impersonate' attribute.
Palbinder Sandher
Software Platform Engineer
T: +44 (0)141 945 8500
F: +44 (0)141 945 8501
http://www.iesve.com
Integrated Environmental Solutions Limited. Registered in Scotland No. S
Why are you using xcopy at all? CopyFile is a thing which exists ->
http://wixtoolset.org/documentation/manual/v3/xsd/wix/copyfile.html
And then your files will be part of uninstall/rollback/upgrade etc without any
extra work.
Palbinder Sandher
Software Platform Engineer
T: +44 (0)141 945 8
http://www.joyofsetup.com/2007/09/24/test-your-setups-virtually/
Palbinder Sandher
Software Platform Engineer
T: +44 (0)141 945 8500
F: +44 (0)141 945 8501
http://www.iesve.com
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Buildin
You can make a patch to update both A -> C and B -> C but I don't think you can
selectively make it also update A to B.
C is the what you specific in the UpgradeImage section of your Patch Family
(the 'destination').
A & B should be specified as TargetImages (the 'source').
e.g.
http://wixtoolset.org/documentation/manual/v3/xsd/wix/product.html
http://msdn.microsoft.com/en-us/library/aa368609.aspx
Palbinder Sandher
Software Platform Engineer
T: +44 (0)141 945 8500
F: +44 (0)141 945 8501
http://www.iesve.com
Integrated Environmental Solutions Limited. Registered in
A very simplistic way to do it would be to add a LaunchCondition to your MSI
which the bootstrapper provides.
Something like
In your MSI and something like
In your bundle should do it.
This is easily defeated by anyone who opens the MSI up using Orca/InstEd! but
it'll
See http://wixtoolset.org/documentation/manual/v3/overview/heat.html
The -t parameter allows you apply an XSLT to post-process the generated XML.
Palbinder Sandher
Software Platform Engineer
T: +44 (0)141 945 8500
F: +44 (0)141 945 8501
http://www.iesve.com
Integrated Environmental Solutio
See http://robmensching.com/blog/posts/2012/8/20/the-wix-toolset-license/
Palbinder Sandher
Software Platform Engineer
T: +44 (0)141 945 8500
F: +44 (0)141 945 8501
http://www.iesve.com
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Bu
See https://msdn.microsoft.com/en-us/library/aa368599.aspx
Palbinder Sandher
Software Platform Engineer
T: +44 (0)141 945 8500
F: +44 (0)141 945 8501
http://www.iesve.com
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Building, Wes
An executable will always be executed as a child process of the process which
launches it. Even if you ship a DLL as your custom action you'll need to call
RunDLL32.exe to actually execute the code.
I don't think this is the question you need to be asking. What are you actually
trying to achiev
Unless the 3rd party installer is an MSI (which from your previous e-mails, it
appears they're executables), Burn won't do that regardless.
If it is an MSI you can set the Visible attribute on the MsiPackage element to
yes & it won't do it either.
Palbinder Sandher
Software Platform Engineer
T
-
From: Matt O'Connell [mailto:techsupport...@gmail.com]
Sent: 09 July 2015 15:22
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Bootstrap conditioned on OSbittage
Ah that's great, and I can hide the bundle ARP itself as well?
On 09/07/2015 11:51, Pally Sandher wrote:
&g
It's a file identifier. Run heat with the -suid option & it will make
more sense (why this isn't default is beyond me). The ! means it will be
translated to a short path name during the install. See
http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx
You probably want to run heat with -s
http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm
Also try looking at a verbose log of your installer during install.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovat
Srivardhan is correct, chaining MSI's isn't supported by Windows Installer (as
far as I know but my knowledge is limited to v3.1 since it's the only version
widely supported from XP onwards. v4.5 or v5 may have different functionality
but until they're provided for Windows XP through automatic u
Quinton I also reported the same issue in the WiX bug tracker on
Sourceforge on issue 2025677 a while ago & was told the same thing as
you can see from the notes on it.
As I wrote on that issue, the workaround Neil outlined below is what
I've implemented and if it works for companies like Perforce
That's strange. The smart-cabbing feature in WiX should reduce the size
of your cabs rather than increase them.
I've just checked a small plug-in installer of ours which puts the same
12 files (3 DLL's. 1 .BMP, 8 .GIF;s) in 2 different locations based on
feature conditions. The cab has 2 copies of
It's a temporary directory created by light during run time for processing
files. It is deleted when light finishes its current process.
Set the environment variable WIX_TEMP to specify your own directory but it has
nothing to do with your ICE error.
Have you searched MSDN for ICE31? I get the f
WiX 3.0 does UI in the same way WiX 2.0 did. The only difference is it's
compiled into a DLL in WiX 3.0 rather than a wixlib & you need to change
your command line for running light.exe accordingly.
The Back/next/whatever buttons should be modified using Publish
Elements. See "Customizing Built-in
I'm not surprised it works when "install the Visual C++ 2008
Redistributable Package (vcredist_x86.exe) before installing my msi".
His app is apparently built in VS2008 (version 9.0) & he's merging the
VS2005 (version 8.0) runtimes into his MSI according to his original
message.
Add the correct me
Is your MSI built as x86 or x64?
Our product has multiple OCX's & COM DLL's which I've harvested using
heat.exe and everything registers fine on both 32-bit & 64-bit O/S.
However all our MSI's are built for x86 as our apps are 32-bit so I've
never run across this issue myself.
If you're building a
Short answer: yes change all your Component GUIDs.
I've got the exact same situation as yourself & having read all the
information available on Component rules I've changed all ours.
If you want to know what happens if you don't change the GUID's read up
on Component Rules & what happens when yo
Something I've never had to use before but looking at my own machine
(XP64) there's a directory at C:\Documents and Settings\All
Users\Documents\ & on my Vista64 VM (potentially Windows 7 too but I
don't have a machine here to check it) there exists a directory at
C:\Users\Public\Documents\ which
When someone volunteers in their own time to write an updated one, yes.
Until then, no.
Some people don't seem get this whole concept of open source
development.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**D
The tutorial is a good place to start as there aren't any differences in the UI
Elements between v2.0 & v3.0, only the linking method which the WiX 3.0
documentation covers anyway as far as I can remember.
Neil Sleightholm has written a very good blog on customising the stock WiX
UI's. Find it a
701 - 800 of 1015 matches
Mail list logo
