Heat /? shows usage. Looks like -ke is keep empty directories. I don't
see a way to exclude files, but maybe somewhere in the mix.


-----Original Message-----
From: CoolBreeze [mailto:coolbreeze...@googlemail.com] 
Sent: Friday, May 13, 2011 11:20 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Excluding file types

I have a couple of questions, I want to find out from the list.

1. Is it possible to exclude certain file types when harvesting files
with
heat? I'm using Wix 3.5 and I have files that I need to harvest from a
Surround repository folder. Surround like Subversion creates .xxxx
files.
I'd like to exclude these files if possible when I harvest the files.

2. During the harvesting of files is it possible to create an empty
directory that gets included in the resulting .wxs file? I need to
include
in my .wxs components file a folder and set permissions on it. I
currently
take the file after it has been created by heat and manually add the
<Directory /> entry.

Thanks.
------------------------------------------------------------------------
------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to