Try the latest weekly build from http://wix.sourceforge.net/releases/.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] On Behalf Of Scott Sam
> Sent: Monday, December 17, 2007 3:51 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Votive
To define the EULA add this to your wxs file:
(For details have a look at the Wix.chm, chapter "Using the WixUI dialog
library")
I'm currently using Wix 3.0.3328.0
Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Levon Levonian
Sent: Thursday
BTW, the German translation for “New folder” is “Neuer Ordner”. I’m
not sure how “Heft” is translated, probably booklet or notebook.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Tuesday, October 17, 2006 5:46 PM
To: Bahar Shah
Cc: wix-users@lis
Windows Installer 3.0 the first version which supports it. It is mentioned
here, too:
http://blogs.msdn.com/windows_installer_team/archive/2006/06/27/648447.aspx
(see rule 45 LUA patching)
Regards,
Martin
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
The Dependencies column of the ServiceInstall table has type Formatted. Maybe
it's possible to use
Properties SVCDEP1 and SVCDEP2 could be set with a custom action which can have
the conditions you need.
Regards,
Martin
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-us
I've written a MSBuild project a couple of days ago to learn how it works.
Looks like this:
http://schemas.microsoft.com/developer/msbuild/2003";>
package
setup
output\
.\tools
Release
setup.wxl
Hi,
if I try your wxs and validate the resulting msi I get
ICE12 ERROR CustomAction: Assign_E_ROOT is of type: 115 referring to a
Directory. Therefore it must come before CostFinalize @ 1000 in Seq Table:
InstallExecuteSequence. CA Seq#: 1002
ICE12 ERROR CustomAction: Assign_C_ROOT is of
We have no plans to use
WiX v3.0 for production until next year. It won’t affect us if you switch
to v2.0 now. When we switch to WiX v3.0 it won’t be a problem to switch
to .Net 2.0 at the same time.
IMHO WiX 3.0 is not
production-ready anyway, but the closer you get to finish it, the
We're using v2.0.3719.0 right now and have no problems so far which require us
to update. We will eventually use WiX 3.0, but not in production this year. We
currently use Votive v2 just to have intellisense for editing WiX files. I
haven't tried Votive v3 yet.
The core v2 toolset and UI lib ar
9 matches
Mail list logo
