Rob the RSS feed for WiX 3.8 hasn't been updating since the 8th. I don't have
the WiX 4.0 feed subscribed to check it.
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
Hi,
We have an installer that has been created by a developer that has since
left the company.
I'm trying to determine how to add a single page at the end of the
installation that displays 'Installation completed', this is simply because
the installation is so quick that it looks like it might
WixUI_Minimal only has an EULA screen in addition to the completed one you want.
-Original Message-
From: Rob Wilson [mailto:netp...@gmail.com]
Sent: April 29, 2013 09:17
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix - A simple 'Completed' page / MSBuild how to configure
I'm migrating the development branch of one of my products from Wix 3.5 and
setup.exe to Wix 3.6 and Burn. I'm having an issue getting the upgrade story
to work.
The upgrade code in both MSI's is the same. The later MSI by itself upgrades
the earlier product no problem.
But when I run the
[05BC:0BF8][2013-04-28T13:03:04]: Detected related package:
{B892ABD4-6B9B-432A-8B31-D849CBEA6969}, scope: PerMachine, version: 7.0.127.0,
language: 0 operation: MajorUpgrade
[05BC:0BF8][2013-04-28T13:03:04]: Detected related package:
{B892ABD4-6B9B-432A-8B31-D849CBEA6969}, scope: PerMachine,
There is only a single MsiPackage element in the chain--the one to be installed:
Chain
!--PackageGroupRef Id=Netfx45Full /
PackageGroupRef Id=Netfx35Full /
RollbackBoundary /--
MsiPackage Id=jXchange Compressed=yes
SourceFile=$(var.jXchangeWix.TargetPath)
Lots of beginning questions here. Apologies if all have been answered before
but I'm burnt out on day 3 of very slow progress. I'm experiencing some
learning-difficulties with WiX. Thus far, I've completed a wxs-file for our
Windows Forms application that creates the installation directories,
Hi All,
Can anyone explain to me what each of these items do (besides the obvious)? Or
perhaps point me to some documentation?
namespace Microsoft.Tools.WindowsInstallerXml.Bootstrapper
{
// Summary:
// Indicates the state desired for an installation package.
public enum
What's unclear? They are pretty self explanatory. Not sure what else to say.
On Mon, Apr 29, 2013 at 11:00 AM, Nick Miller nmil...@livetechnology.comwrote:
Hi All,
Can anyone explain to me what each of these items do (besides the
obvious)? Or perhaps point me to some documentation?
Maybe he wants to know what happens when any of the RequestState values are
selected/set/used?
If there's any documentation on it, I'd imagine that would have the relevant
info.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: April 29, 2013 14:11
To:
Correct, so for example, what is the difference between Absent, and
ForceAbsent? Does selecting None do anything? Do they behave differently
depending on the action launched (Install/Uninstall/Repair)?
-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: Monday,
1. ForceAbsent forces a package to be Absent when Absent would not (aka:
permanent is set).
2. None says do nothing with the package.
3. No, that would be confusing. smile/
I guess ForceAbsent could use documentation. I think it's in the .h file
for the native code, not the managed code since the
Resending because I haven't received any replies to this last post.
Is the below behavior a bug with the Wix burn bootstrapper functionality?
-Original Message-
From: Christopher West C [mailto:christopher.c.w...@ericsson.com]
Sent: Wednesday, April 24, 2013 4:26 PM
To: 'General
Thanks for the reply Rob,
Let me see if I understand this correctly. If in my chain I have MSI-1 and
MSI-2, and I set RequestState.None for MSI-2 will it skip over that package
completely?
Thanks,
Nick
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent:
IIRC, yes, exactly.
On Mon, Apr 29, 2013 at 12:10 PM, Nick Miller nmil...@livetechnology.comwrote:
Thanks for the reply Rob,
Let me see if I understand this correctly. If in my chain I have MSI-1
and MSI-2, and I set RequestState.None for MSI-2 will it skip over that
package completely?
Awesome, thanks!
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, April 29, 2013 4:24 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RequestState
IIRC, yes, exactly.
On Mon, Apr 29, 2013 at 12:10 PM, Nick Miller
I wrote a custom managed BA, and got most of the functionality to work,
expect for a repair. Examining the bundle log provides:
[335C:3440][2013-04-29T13:51:41]w343: Prompt for source of package:
NetFx45Web, payload: NetFx45Web, path:
D:\dev\Setup\redist\dotNetFx45_Full_setup.exe
17 matches
Mail list logo
