Neil Sleightholm wrote:
> Thanks for the clarification. Does that mean that the binder information is
> only updated by light? If so what happens to a wixlib with embedded files,
> does light extra the files to get the version information?
>
Yes. When files are bound into a .wixlib, they go t
AIL PROTECTED]>
From: [EMAIL PROTECTED] on behalf of Bob Arnson
Sent: Sun 13/07/2008 22:32
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Assembly file versions in wixlibs
Neil Sleightholm wrote:
> Not according to the help
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).
--
ssion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Assembly file versions in wixlibs
Neil Sleightholm wrote:
> Thanks, I added the following:
>
> Assembly=".net">
>Value="!(bind.assemblyFileVersion.File.dll)" />
>
>
There's
D]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: 13 July 2008 19:11
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Assembly file versions in wixlibs
Neil Sleightholm wrote:
> Thanks, I added the following:
>
> Assembly
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/
-
:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: 13 July 2008 06:15
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Assembly file versions in wixlibs
It'll look something like:
I think.
t.
Subject: Re: [WiX-users] Assembly file versions in wixlibs
>>3. You should be able to get the behavior you want by manually adding
the AssemblyName element and refer to the !(wix. FileVersion.FileId).
Do you have any pointers to samples to get m
>>3. You should be able to get the behavior you want by manually adding
the AssemblyName element and refer to the !(wix. FileVersion.FileId).
Do you have any pointers to samples to get me started?
Neil
-
Sponsored by: Sour
ion for Windows Installer XML toolset.; General discussion
for Windows Installer XML toolset.
Subject: Re: [WiX-users] Assembly file versions in wixlibs
I am already using publisher policy files but they don't work in a daily build
environment. We have publisher files for going from v1.00 t
ted
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
From: [EMAIL PROTECTED] on behalf of Rob Mensching
Sent: Fri 11/07/2008 09:46
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Assembly file versions in wixlibs
You'
nstaller XML toolset.; General discussion
for Windows Installer XML toolset.
Subject: Re: [WiX-users] Assembly file versions in wixlibs
Thanks Rob, I'll take a look at 3.
Sorry to go on about it but why would making -fv the default be a problem? If
you are doing the "right" thing then
8
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Assembly file versions in wixlibs
1. Note in my original comment: "One more legacies of Fusion and its, IMHO,
under-informed design choices." I agree with you. I very strongly believe that
Fusion
Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Sleightholm
Sent: Thursday, July 10, 2008 14:50
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Assembly file versions in wixlibs
I think I might have replied in hast, in my opi
ndows Installer XML toolset.
Subject: Re: [WiX-users] Assembly file versions in wixlibs
I understand the issues but I was answering the question "why isn't -fv
the default" (sorry, if that wasn't clear). It's not the default
because it isn't the recommended way to u
t: Saturday, July 05, 2008 16:19
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Assembly file versions in wixlibs
If it is not the "correct way" how come Microsoft do it all the time!
The issue is that if you do nightly builds to ensure compatibility with
ot
er Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
--- On Sat, 7/5/08, Immo Landwerth <[EMAIL PROTECTED]> wrote:
> From: Immo Landwerth <[EMAIL PROTECTED]>
> Subject: RE: [WiX-users] Assem
ilto:[EMAIL PROTECTED] On Behalf Of Christopher
Painter
Sent: Sonntag, 6. Juli 2008 00:37
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Assembly file versions in wixlibs
There are perfectly valid and correct scenarios where one would need to
update the Assembly
bject: Re: [WiX-users] Assembly file versions in wixlibs
Using "-fv" is not the "correct way" to install files into the GAC. The
"correct way" is to update the Assembly version not the assembly file
version. One more legacies of Fusion and its, IMHO, under-informed
desig
t;[EMAIL PROTECTED]> wrote:
> From: Rob Mensching <[EMAIL PROTECTED]>
> Subject: Re: [WiX-users] Assembly file versions in wixlibs
> To: "General discussion for Windows Installer XML toolset."
>
> Date: Saturday, July 5, 2008, 5:05 PM
> Using "-fv&quo
Using "-fv" is not the "correct way" to install files into the GAC. The
"correct way" is to update the Assembly version not the assembly file version.
One more legacies of Fusion and its, IMHO, under-informed design choices.
You might try and see if a binary .wixlib (pass "-bf" switch) gets yo
21 matches
Mail list logo
