Hi,
I've probably run into a bug with the latest WIX 3.6 build (see issue
https://sourceforge.net/tracker/?func=detailaid=3521939group_id=105970atid=642714)
on SourceForge.
Basically, I've an MSI which installs a file in a per-user scenario:
?xml version=1.0 encoding=UTF-8?
Wix
Hi All,
I'm trying to perform a major upgrade for my installer, and use Upgrade
table to detect the existing installer version.
/Upgrade Id=$(var.UpgradeCode)
UpgradeVersion Minimum=$(var.ProductVersion)
IncludeMinimum=no OnlyDetect=yes Property=NEWERVERSIONDETECTED /
Ah I probably wasn't clear. v1 had Product Code A, v2 has Product Code B. Hence
I have a upgrade patch for versions 2.0 or 2.1 - 2.2 while a Major Upgrade for
1.x - 2.x
Patching works fine now with Burn using the MSP, however for anyone who doesn't
have any version of this product installed or
Hi Focks:
I think I've found a bug in wix 3.6:
I'm trying to create a solution that allows building two msi's one x86 and one
x64.
I have to following in my package element to this end:
Package
InstallerVersion=300
Compressed=yes
InstallScope=perMachine
Hello,
My Bootstrapper application needs to have parallel download and
installation, which Burn doesn't support as far as I know.
I've implemented my own downloader that alerts Burn when the file is
downloaded. I put a Retry in ResolveSource, and it calls that until it gets
a flag telling it to
Rob this is what I get when I click Uninstall from ARP then click Uninstall
in the Burn dialog - http://upload.iesve.com/downloads/uninstall.png
The MSI isn't anything complex, it's using a completely unmodified
WiXUI_InstallDir for UI.
Palbinder Sandher
Software Platform Engineer
T: +44 (0)
It's not really 'dogfooding' as I've never written any of the WiX code =)
I've been using WiX since Summer 2006 which was v2.0 didn't move to v3.0
until around Summer 2008 followed by v3.5 in Autumn 2010 lived on the
cutting edge with all 3 versions. I would've moved to WiX v3.6 sooner but we
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 Virtual Environment**
Integrated
Use the arch switch on the candle coomand-line and remove the Platform
attribute.
On Fri, Apr 27, 2012 at 5:10 AM, Sean Farrow
sean.far...@seanfarrow.co.ukwrote:
Hi Focks:
I think I've found a bug in wix 3.6:
I'm trying to create a solution that allows building two msi's one x86 and
one x64.
Yes,. use the WixFailWithSuccess (named something like that) custom
action.
On Fri, Apr 27, 2012 at 2:53 AM, shengyixing shengyix...@hotmail.comwrote:
Hi All,
I'm trying to perform a major upgrade for my installer, and use Upgrade
table to detect the existing installer version.
/Upgrade
In fact, if you add it to iexplore and firefox which usually close, nothing
gets close. Is there any way around this? I presume this is outside Wix
domain since chrome does show up in FilesInUse.
Respectfully,
Tim
--
Live
Burn supports paralllel download. The setting is named something just like
that on the Chain element.
On Fri, Apr 27, 2012 at 5:38 AM, Miss Parker caisa.westl...@gmail.comwrote:
Hello,
My Bootstrapper application needs to have parallel download and
installation, which Burn doesn't support as
Will do Heath, thanks for resolving it so quickly.
Apologies for not getting time to get some detailed debug info using the PDBs
as Bob requested, was planning on making some time for doing it this afternoon
but it's a moot point now =)
Palbinder Sandher
Software Platform Engineer
T: +44 (0)
Hello all,
Is it possible to use/create a link in a dialog window? I would like to have
a link to a support website in a localized dialog window.
Thank you.
--
View this message in context:
The wixstdba does not show special UI for upgrade scenarios. It just shows
install (or an error message if it thinks it will downgrade what is on the
machine).
That said, it should remove the previous Bundle when installing the new
one. Can you share out more of the log? The part that shows the
Yes. MSI 5.0 (I think 5.0 was the first) supports it.
On Fri, Apr 27, 2012 at 8:09 AM, victorwhiskey victorhwhis...@yahoo.comwrote:
Hello all,
Is it possible to use/create a link in a dialog window? I would like to
have
a link to a support website in a localized dialog window.
Thank you.
Hi Rob,
yes, my fault. I was under the impression that there should be a custom UI for
upgrades.
Couldn't reproduce the issue with the duplicate ARP entry, so I closed the bug.
Kind regards,
Henning
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Friday,
Is there a way to specify that in visual studio?
Cheers
Sean.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 27 April 2012 15:37
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] bug in wix 3.6?
Use the arch switch on the
IIRC, by default it picks it up from your VS Configuration.
On Fri, Apr 27, 2012 at 9:04 AM, Sean Farrow
sean.far...@seanfarrow.co.ukwrote:
Is there a way to specify that in visual studio?
Cheers
Sean.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 27
So if I have a solution that has an x64 platform, and don't include a platform
attribute, would this work?
Cheers
Sean.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 27 April 2012 17:12
To: General discussion for Windows Installer XML toolset.
Subject: Re:
Leave $var.platform in your Package@Platform then in the solution
configuration manager make sure you set the platform correctly for the
relevant project.
-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: 27 April 2012 17:33
To: General discussion for
Last time I looked at the WiX .targets files I noticed that they create an
InstallerPlatform property that is passed to candle. The InstallerPlatform
property can be explicitly set in your .wixproj. When it is not explicitly set,
the WiX .targets files use the Platform property to determine
Hi:
I am building one msi for x86, and x64 from the same project. If I am
interpreting you correctly, I can let visual studio create the new solution
platform for me.
Please correct me if I'm wrong!
Cheers
Sean.
-Original Message-
From: Castro, Edwin G. (Hillsboro)
On 27-Apr-12 10:32, Pally Sandher wrote:
I'm quite happy to use the cutting edge (in some ways it's preferable) but I
get a little irked when things I've been led to believe are the standard ways
of doing things with Windows Installer by yourself other WiX
contributors/developers are
That is correct. You will still need to build twice as only one platform gets
built at a time.
You'll want to take a look at what projects are selected for each solution
platform and make decisions about how to build your solution. Perhaps you need
to build 3 times: AnyCPU, x86, x64.
Edwin G.
If it's a .Net assembly of managed code, then you would use RegAsm
(internally). If it's a native binary, then you would use regsvr32
(internally).
The reason I say internally is the ability to control what they create
or remove is out of your hands if you depend on these tools. This is why
Hi:
And where finally can I see what is building for what platform?
I know I can see but don't know where!
Cheers
Sean.
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: 27 April 2012 20:02
To: General discussion for Windows Installer XML
Option 1: Select Configuration Manager from the Build menu.
Option 2: Select Configuration Manager... from the solution context menu in
Solution Explorer or Solution Navigator.
Option 3: Select Configuration Manager... from the Solution Configurations drop
down on the Standard toolbar
In the
Is the WiX Standard Bootstrapper Application compatible with Windows 2000? My
individual MSI packages all work fine but all my bundles fail immediately even
if I save them to a local folder: [bundleName].exe is not a valid Win32
application.
Target Machine:
Win2K Pro SP4 w/KB891861 'roll up'
I have just rebuilt my x86/x64 project without the Package/@Platform attribute
in VS and it does build correctly. I needed to build both x86 x64 at the same
time so I could reference them in a burn project, to do this I duplicated my
wixproj file and set one as an x86 build and the other as
No. Windows 2000 is not supported by the VS 2010 CRT. Windows XP (I think
SP1+).
On Fri, Apr 27, 2012 at 2:34 PM, Rich Dingle rdin...@accelitec.com wrote:
Is the WiX Standard Bootstrapper Application compatible with Windows 2000?
My individual MSI packages all work fine but all my bundles fail
31 matches
Mail list logo
