uot;[SourceDir]" SourceName="custom-logo.png "
> DestinationDirectory="APPLICATIONROOTDIRECTORY"/>
> On="uninstall" />
>
>
> -Original Message-
> From: Andrew Maxwell [mailto:andrew.maxw...@papercut.com]
> Sent:
on that would evaluate a custom property to
> determine if it needs to be installed. Then in your installer you would
> have a custom action which would enable the component (via a property)
> if the file exist in the installation media.
>
> -Original Message-
> From: An
> external UI.
>
> On Mon, May 21, 2012 at 7:42 PM, Andrew Maxwell <
> andrew.maxw...@papercut.com
> > wrote:
>
> > Hi all,
> > I've got a scenario where in some cases a file may be included in our
> > distribution, but if it's not - no big deal, the
Hi all,
I've got a scenario where in some cases a file may be included in our
distribution, but if it's not - no big deal, the installation should
continue on anyway.
At the moment I've got the file flagged as Vital="no" , and this achieves
my goal - except for a popup asking to retry/cancel/ignor
source folder set to a
> pre-processor variable, e.g.:
> Source="$(var.SourceFiles)\File1.exe" />
>
> You can then set this a compile time.
>
> Neil
>
> -Original Message-
> From: Andrew Maxwell [mailto:andrew.maxw...@papercut.com]
> Sent: 18
Hi again all,
My last post was a bit of a brain-dump, so I can boil my question down to a
few points here: :)
- using heat, is there a way to harvest a directory and suppress directory
id/name insertion in the resulting .wxs? (when automating heat output ,
this is an annoyance)
eg . heat.exe dir
Hi fellow Wixians,
I've been tasked with automating MSI creation , tying it into our build
processes, and running into some grief with heat.
So, I've got two questions for the list:
a) There doesn't seem to be a way to fully automate the process from
directory harvest all the way through to msi
7 matches
Mail list logo
