Hi all,
We use normally the same ProductCode + UpgradeCode for x86 and x64
packages and exclude them by using a launch condition. (I know not
Windows Installer recommended but due to sake of simplicity e.g. when
creating two MSIs from one InstallShield solution done that way). Same
as now for WiX
On 08-Aug-12 11:30, Tobias S wrote:
> We use normally the same ProductCode + UpgradeCode for x86 and x64
> packages and exclude them by using a launch condition. (I know not
> Windows Installer recommended but due to sake of simplicity e.g. when
It's not a recommendation; it's a requirement:
"The
On 07-Aug-12 17:23, John M. Wright wrote:
> Did a sourceforge bug get created from the below email? If so, can you
> point me to it so I can monitor it's status? If not, can one be generated?
No. Feel free to file one.
> In my case, I'm performing custom prerequisite checks that require elevated
>
Hi,
I'm working with the latest WIX version (v3.6.3206.0).
Unhandled exception at 0x0FF45EE6 (wixstdba.dll) Setup.exe: 0xC005:
Access violation reading location 0x0018.
After downloading the symbols from Wixtoolset.org, Visual Studio pinpointed
the exception to WixStandardBootstrapperApp
On 08-Aug-12 12:00, Henning Krause wrote:
> Unhandled exception at 0x0FF45EE6 (wixstdba.dll) Setup.exe: 0xC005:
> Access violation reading location 0x0018.
Please file a bug so it doesn't get lost in e-mail.
--
sig://boB
http://joyofsetup.com/
---
Hi Bob,
done:
https://sourceforge.net/tracker/index.php?func=detail&aid=3555380&group_id=105970&atid=642714
Kind regards,
Henning
> -Original Message-
> From: Bob Arnson [mailto:b...@joyofsetup.com]
> Sent: Wednesday, August 08, 2012 6:32 PM
> To: wix-users@lists.sourceforge.net
> Subje
Does this crash happen at the end of the install? My users have reported a
problem when upgrading today and I updated the build to 3.6.3206 yesterday and
wonder if this is the same issue.
Neil
-Original Message-
From: Henning Krause [mailto:m...@henningkrause.eu]
Sent: 08 August 2012 1
Hi Neil,
no, it happens rather in the middle of it...
Kind regards,
Henning
> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: Wednesday, August 08, 2012 7:11 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn: Wi
That could be similar - the user report was a little vague! (I find my msi is
installed but then the burn UI doesn't return. I think I'll rollback to an
earlier release.
Neil
-Original Message-
From: Henning Krause [mailto:m...@henningkrause.eu]
Sent: 08 August 2012 18:21
To: General d
I managed to reproduce the problem and downgrading to v3.6.3109.0 fixes it.
Neil
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 08 August 2012 18:36
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn: WixStdBA crashes wih
Hello,
I'm working on an installer that requires numerous roles and features to be
enabled. If those components are not available, the system, consisting of web
applications, MSMQ, and SMTP server will fail to install, never mind run.
Does WIX 3.6 support checking whether a Windows feature is
Hello,
I wrote a native bootstrapper (using std win32 dialogs, rather than themes)
which requests some data from users before proceeding to install and configure
the product. This includes requesting the top level domain for websites and
keys used to encrypt registry entries. Without it, insta
12 matches
Mail list logo
