product core, with outside pieces.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: February-21-2013 2:20 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLib not behaving as desired
Did you have a Property in the Fragment
gt; >
> > NOT
> > Installed
> >
> >
> > NOT
> > Installed
> >
> >
> >
> > I have 15 or so prerequisite fragments and a binary fragment within
> > the same file.
> >
> > -Original Message-
>
: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLib not behaving as desired
I think use of PropertyRef is awesome in that case. If you didn't have the
Condition (which uses the Property) I might consider using CustomActionRef
instead. But I like PropertyR
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Wednesday, February 20, 2013 3:27 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] WixLib not behaving as desired
>
> I've yet to see a c
.
Subject: Re: [WiX-users] WixLib not behaving as desired
I've yet to see a case where real content didn't exist in a Fragment that could
be referenced.
On Wed, Feb 20, 2013 at 1:12 PM, Hoover, Jacob
wrote:
> This smells like a need for a FragmentRef, which I currently work
&g
Mensching [mailto:r...@robmensching.com]
> Sent: February-20-2013 4:01 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] WixLib not behaving as desired
>
> If references are broken, the linker would tell you it couldn't find a
>
@robmensching.com]
> Sent: Wednesday, February 20, 2013 3:01 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] WixLib not behaving as desired
>
> If references are broken, the linker would tell you it couldn't find a
> symbol. I think yo
?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: February-20-2013 4:01 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLib not behaving as desired
If references are broken, the linker would tell you it couldn't find a
symb
so I don't know if that is
possible.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, February 20, 2013 3:01 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLib not behaving as desired
If references
rectory section.
> How do I know if the references are not broken?
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: February-20-2013 3:28 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] WixLib not beha
Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLib not behaving as desired
References flow from the Product element down. Follow your references.
There isn't enough below to really know what is wrong.
On Wed, Feb 20, 2013 at 12:20 PM, Marc Beaudry wrote:
> Hopefully this
Y]MyBinary.exe"
> WorkingDirectory='APPLICATIONROOTDIRECTORY' >
> SourceFile="SomeIconFile.ico"
> />
>
> Key="Software\Microsoft\[Manufacturer]\[ProductName]" Name=&qu
: February-20-2013 3:04 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLib not behaving as desired
It all depends on what is in your Fragments and what is referencing what.
My guess is by moving the Shortcut, you removed the reference to oen or more
Fragme
It all depends on what is in your Fragments and what is referencing what.
My guess is by moving the Shortcut, you removed the reference to oen or
more Fragments in you .wixlib.
On Wed, Feb 20, 2013 at 12:00 PM, Marc Beaudry wrote:
> I have a lib file that contains a bunch of files and a desktop
14 matches
Mail list logo