OK... So this, I don't get...
Given:
Which *obviously* does not exist :-)
Why does:
IT_EXISTS AND NOT Installed
Get invoked?
Thanks!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Amir
Kolsky
Sent:
For #2 you also have to add a reference to WiXUiExtension.dll. Since you are
using Visual Studio integration right click on the References node in Solution
Explorer and select Add Reference. Then find WixUiExtension.dll in the list and
click add. Close the dialog and build and things should work
I installed the latest beta of WiX 3 because I want to use the Visual Studio
integration. I've run into some problems getting started. I'm hoping that
I can get some assistance.
1) The text of error messages are not being displayed in VS 2005. When the
build fails, I have to build from a comman
Neil Sleightholm wrote:
> Not according to the help file, in the "Binder Variables" topic
> bind.assemblyFileVersion.FileID is listed. Is the help file wrong or is
> there still a bug?
>
The doc should be clarified: That's available only when the assembly
file version was gathered (-fv).
--
Anthony Bouch wrote:
> I was wondering what my options were for trying to produce a .exe from the
> .msi
Take a look at setupexe.
> - mainly so that Vista users can right-click and "run as Administrator"
> (should they want to - if we leave aside the security issue for a moment).
>
MSI produ
Actually this raises another issue, using an invalid binder variable
does report any errors. I guess that really is a bug, I'll add a report.
Neil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: 13 July 2008 19:11
To: General discussion f
Not according to the help file, in the "Binder Variables" topic
bind.assemblyFileVersion.FileID is listed. Is the help file wrong or is
there still a bug?
I changed to bind.fileVersion.FileID and it works. Thanks for the help.
Neil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAI
Hi All
I'm a newbie (but definitely a convert) to WiX. I've successfully create a
fairly advanced WiX script with some help from a sample project. Also
building fine from NAnt.
I was wondering what my options were for trying to produce a .exe from the
.msi - mainly so that Vista users can right-c
Christopher Karper wrote:
> Apparently, I was having a version issue. It's not reported nicely, but
> something, somewhere was mismatched.
Check out fuslogvw --
http://msdn.microsoft.com/en-us/library/e74a18c4.aspx.
--
sig://boB
http://joyofsetup.com/
---
Neil Sleightholm wrote:
> Thanks, I added the following:
>
> Assembly=".net">
>Value="!(bind.assemblyFileVersion.File.dll)" />
>
>
There's no such binder variable. Use fileversion.{0} where {0} is the
file id.
--
sig://boB
http://joyofsetup.com/
-
Daniel Wang (CIS) wrote:
> I'm using the 2.0.5805.0 tools set for wix. I'm authoring an installer for
> 64-bit components, and using the Install Dir UI. I've noticed the odd
> behavior that when you browse to select Program Files it always redirects to
> Program Files (x86) the same when manuall
John Daintree wrote:
> How would I skip the CollectUserInformationDlg and go directly from
> LicenseAgreementDlg to InstallDirDlg, based on the value of a property?
>
The wizard sequence is set by control events in the Next and Back
buttons. Conditionally skipping over a dialog means you nee
Ilya Slobodin wrote:
> 1. Get the patch installed and
> 2. Keep the database file and
> 3. Keep using the MoveFile table to backup the database
>
> I have nothing against using REINSTALL & REINSTALLMODE. But, if set,
> MoveFile to Component action state relationship is broken, file is moved but
>
Thanks, I added the following:
But it seems there may be a bug in the evaluation of binder variables
with lit/light or wixlibs. When I compile the wixlib it contains
fileVersion="!(bind.assemblyFileVersion.File.dll)" which I wouldn't
expect, I would have thought it should be evaluated. But m
14 matches
Mail list logo
