Re: [WiX-users] Using heat.exe with static Components
I've wrote a XSL transform once to add the element for the responsible for the exe. That was not pretty. Much easier to use the XSL transform to exclude the as Neil suggested. Depending on your heat command line you might need to exclude the and a . Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: Neil Sleightholm [mailto:n...@x2systems.com] > Sent: Wednesday, June 16, 2010 10:04 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Using heat.exe with static Components > > For the .net component you could apply a XSL transformation to the file > heat generates - heat will even apply it for you. > > For the service you could do the same but it might be easier to script > the service code and file install and use the XSL transform to exclude > this file from you harvested code. > > Neil > > -Original Message- > From: Andy Clugston [mailto:clug...@gmail.com] > Sent: 16 June 2010 16:53 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Using heat.exe with static Components > > I am trying to work through some automation scenarios regarding heat and > some file-dependent Components. Here is the scenario... I have a > product > that consists of a set of .exes and dlls. I would like to use heat.exe > to > automatically generate these deliverables for me at build time. It does > this well, but there are a few issues that I need to overcome. > > One of the .exes needs to be installed as a service. Since the service > .exe > is always the same, I was wondering if there was a clever way to have a > static .wxs define the element for this .exe? For > instance, can I simple create a Component with the element > without > actually installing the .exe, but rather just reference the name of the > .exe > and path via constructs? > > Similarly, I would like to do the same for a .dll that needs to be > installed > into the GAC. Have the actual .dll be harvested via heat, but have > static > additional configuration to the element reside outside of the > dynamically generated .wxs that heat creates. > > Thank you. > > -- > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using heat.exe with static Components
For the .net component you could apply a XSL transformation to the file heat generates - heat will even apply it for you. For the service you could do the same but it might be easier to script the service code and file install and use the XSL transform to exclude this file from you harvested code. Neil -Original Message- From: Andy Clugston [mailto:clug...@gmail.com] Sent: 16 June 2010 16:53 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Using heat.exe with static Components I am trying to work through some automation scenarios regarding heat and some file-dependent Components. Here is the scenario... I have a product that consists of a set of .exes and dlls. I would like to use heat.exe to automatically generate these deliverables for me at build time. It does this well, but there are a few issues that I need to overcome. One of the .exes needs to be installed as a service. Since the service .exe is always the same, I was wondering if there was a clever way to have a static .wxs define the element for this .exe? For instance, can I simple create a Component with the element without actually installing the .exe, but rather just reference the name of the .exe and path via constructs? Similarly, I would like to do the same for a .dll that needs to be installed into the GAC. Have the actual .dll be harvested via heat, but have static additional configuration to the element reside outside of the dynamically generated .wxs that heat creates. Thank you. -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Using heat.exe with static Components
I am trying to work through some automation scenarios regarding heat and some file-dependent Components. Here is the scenario... I have a product that consists of a set of .exes and dlls. I would like to use heat.exe to automatically generate these deliverables for me at build time. It does this well, but there are a few issues that I need to overcome. One of the .exes needs to be installed as a service. Since the service .exe is always the same, I was wondering if there was a clever way to have a static .wxs define the element for this .exe? For instance, can I simple create a Component with the element without actually installing the .exe, but rather just reference the name of the .exe and path via constructs? Similarly, I would like to do the same for a .dll that needs to be installed into the GAC. Have the actual .dll be harvested via heat, but have static additional configuration to the element reside outside of the dynamically generated .wxs that heat creates. Thank you. -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
