Markus, The heat.exe has a switch -t:<transform.xsl>. If you specify this switch running heat, the 'transform.xsl' will be applied to the regular output of you heat command. The final resulting wxs file will contain transformed xml.
There are no special requirements for that XSL transform. Hope this helps, -- Yan -----Original Message----- From: Markus Gaugusch [mailto:w...@gaugusch.at] Sent: Thursday, December 10, 2009 10:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to specify files in Installer package Hi Rob! Do you mean, that you use xslt to modify the heat-generated wxs files in an automated way? Can you give me an example for that? br, Markus On Dec 9, Rob Mensching <r...@robmensching.com> wrote: > I usually just write an XSL transform. heat supports that. > > On Wed, Dec 9, 2009 at 9:45 PM, Blair <os...@live.com> wrote: > >> Two ideas that come to mind: One is to use msbuild to call heat (or some >> other system that can calculate a list of files given an exclusion pattern) >> and the other is to write an extension to heat. >> >> -----Original Message----- >> From: Markus Gaugusch [mailto:w...@gaugusch.at] >> Sent: Wednesday, December 09, 2009 12:56 PM >> To: wix-users@lists.sourceforge.net >> Subject: Re: [WiX-users] How to specify files in Installer package >> >> Hi Blair! >> >> Those directories contain many files and I don't want to specify them by >> hand. >> And if I want to ignore .svn directories, I'm fully out of luck. >> Additionally, I tried to split up my project into several trees like that: >> - framework\bin (common binary files, xml schema, ...) >> - framework\config (common config files) >> - frameworkexe\bin (common executables) >> - project\bin (project specific xml files, config files ...) >> - project\config (project specific configuration files) >> - projectexe\bin (project specific exe files) >> >> They should all go into ...\bin and ...\config on the destination machine. >> Unfortunately, the "bin" and "config" directories would conflict when I run >> light.exe because they have the same name and heat generates the same >> component >> id for both of them (which is ok because they are he same directory on the >> destination machine). If I could tell heat to use an existing reference for >> some directories and create the others, it might also work, but I think >> this >> is >> not a clean solution. >> >> So, if I want to use heat.exe, I need to use a single tree of source files >> or >> split my project into parts that have no common directories at all (which >> does >> not meet my requirements). >> >> To solve my problems I can only imagine to use a single source tree for the >> installer package and tell heat to ignore certain files and take all >> others. >> Or >> do you have a better idea? >> >> Thanks! >> Markus >> >> On Dec 9, Blair <os...@live.com> wrote: >> >>> Can you call heat per-file instead of per-dir for those directories? >>> >>> -----Original Message----- >>> From: Markus Gaugusch [mailto:w...@gaugusch.at] >>> Sent: Wednesday, December 09, 2009 1:47 AM >>> To: wix-users@lists.sourceforge.net >>> Subject: [WiX-users] How to specify files in Installer package >>> >>> Hi, >>> >>> I'm using WIX3 and try to make an installer package for our software. >>> The software contains lots of files and folders, and some of them have >> to >>> be treated specially (one for installing a Windows Service, several >> config >>> files which should be preserved). >>> >>> Now I'm using heat to generate the list of files for my package, but I >>> don't want to edit the generated content in order to specify my service >> or >>> config files. >>> At the moment I remove those files from heat generated code and have >> them >>> in another file. But this is a manual and error-prone process. >>> >>> I'd like to tell heat to ignore some files and generate the wxs file for >>> everything else. This is especially interesting because I'm using >>> subversion and I can't checkout the files for my installer packages in >> the >>> usual way, because heat would include the .svn directories. >>> >>> I've added a tracker entry, but there was no reaction yet. >>> >> >> https://sourceforge.net/tracker/?func=detail&aid=2900555&group_id=105970 &ati >>> d=642717 >>> >>> Comments? >>> >>> thanks, >>> Markus >> >> >> ------------------------------------------------------------------------ ---- >> -- >> Return on Information: >> Google Enterprise Search pays you back >> Get the facts. >> http://p.sf.net/sfu/google-dev2dev >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> >> ------------------------------------------------------------------------ ------ >> Return on Information: >> Google Enterprise Search pays you back >> Get the facts. >> http://p.sf.net/sfu/google-dev2dev >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> > > > -- __________________ /"\ Markus Gaugusch \ / ASCII Ribbon Campaign markus(at)gaugusch.at X Against HTML Mail / \ ------------------------------------------------------------------------ ------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
