L PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Christopher Karper
> Sent: Thursday, July 31, 2008 19:48
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Binder variables from Votive
>
> It's in the merge module itself. I would have
Bug. Would you mind filing it?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Karper
Sent: Thursday, July 31, 2008 19:48
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Binder variables from Votive
It&#
1, 2008 11:02
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Binder variables from Votive
3.0.4325
On Thu, Jul 31, 2008 at 1:51 PM, Rob Mensching
<[EMAIL PROTECTED]>wrote:
> What version of the WiX toolset?
>
> -Original Message-
&g
It's in the merge module itself. I would have expected it to get
modularized like all of my other file/component references, but alas,
alack... it was not to be.
Chris
On Thu, Jul 31, 2008 at 5:40 PM, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Christopher Karper wrote:
> > It's a merge module, and
Christopher Karper wrote:
> It's a merge module, and the file id needs the GUID put in to work. I
> wouldn't think that was how it's *supposed* to work, but adding the package
> guid to the file id in the binder variable makes it work...
>
Is the !(bind...) in the merge module itself or are y
oolset?
> >
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:
> > [EMAIL PROTECTED] On Behalf Of Christopher Karper
> > Sent: Thursday, July 31, 2008 10:16
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-user
Windows Installer XML toolset.
Subject: Re: [WiX-users] Binder variables from Votive
3.0.4325
On Thu, Jul 31, 2008 at 1:51 PM, Rob Mensching
<[EMAIL PROTECTED]>wrote:
> What version of the WiX toolset?
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PR
2008 10:16
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Binder variables from Votive
>
> Neither of these worked. I don't understand why *none* of the binder
> variables are working. I tried this for my x86 and x64 configs to make
> sure
>
What version of the WiX toolset?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Karper
Sent: Thursday, July 31, 2008 10:16
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Binder variables from Votive
Neither of these worked. I don't understand why *none* of the binder
variables are working. I tried this for my x86 and x64 configs to make sure
it wasn't a platform issue. I get the same issue either way though.
Thanks for the ideas.
Chris
On Thu, Jul 31, 2008 at 12:06 PM, Bob Arnson <[EMAIL
Christopher Karper wrote:
> I still can't get any of these binder variables to work. Does anyone have
> some time to take a look at it? Thanks in advance. :-D
>
Two random things to try:
1. Rename the File/@Id so it doesn't have a dot in it. (The RegEx looks
right, but...)
2. Try putting th
to the root
> of it.
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Christopher Karper
> Sent: Thursday, July 24, 2008 14:12
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Binder va
bject: Re: [WiX-users] Binder variables from Votive
I copied the FileId from the File's ID into the binder variable. Then I
double checked the spelling, then I triple checked it. That was my first
big theory.
Just to help out, here's the pertinent pieces...
Any ideas?
Chris
On Behalf Of Christopher Karper
> Sent: Thursday, July 24, 2008 10:50
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Binder variables from Votive
>
> I'm trying to update my MMC Snap In installer to automatically pull
, 2008 10:50
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Binder variables from Votive
I'm trying to update my MMC Snap In installer to automatically pull version
info from the managed snap-in dll. I've used the variable
"!(bind.assemblyFullName.SampleSn
I'm trying to update my MMC Snap In installer to automatically pull version
info from the managed snap-in dll. I've used the variable
"!(bind.assemblyFullName.SampleSnapIn.dll)" to get the fullname, but in
Orca, it has the actual binder variable text in the registry table, instead
of the replaced
16 matches
Mail list logo
