Hey Paul,
Please excuse the brevity of my reply. I agree there needs to be some
additional tutorials on the heat.exe tool. Below is a quick way of
"harvesting" a directory. Mind you, this is a somewhat repeatable process.
The largest issue would be around the addition or removal of files into the
MSI. If you can guarantee that your file base will say static (rarely the
case) then you could use the below with a fair amount of confidence.
Mind you, understanding how heat.exe works also means that you understand
the composition of a .wxs file and generally how the core tools in WiX work
together (candle.exe, light.exe and others).
1. heat.exe -?
2. Look for the -ag, -template:, -cg and -srd switches.
3. heat.exe dir {C:\SomeDir} -ag -cg MyComponentGroup -srd -template:product
-out MyTest.wxs
4. Open MyTest.wxs and edit the Product and Package information for your
needs. Continue editing as you see fit for Features and other details
including UI.
5. Compile the .wxs using candle.exe and then link using light.exe. The
result should be a MSI.
For some more details check out my blog if you haven't already done so,
especially http://bit.ly/atX0r.
Thanks,
Brian Rogers
"Intelligence removes complexity." - Me
http://blogs.msdn.com/icumove <-- NEW
On Mon, Aug 17, 2009 at 7:28 AM, Paul Crowley <[email protected]> wrote:
> Does anyone have a very simple example of how one might actually use
> Heat in practice? The documentation and the tutorial discusses how Heat
> can handle all sorts of complex cases, but I can't work out what I'm
> supposed to do with the generated file in the simplest case. What I'm
> looking for is something very like the first, simplest example in the
> WiX tutorial, but using Heat - end to end and step by step.
>
> I can only assume that this isn't already there because it seems too
> obvious to discuss, but I'm afraid it wasn't obvious to me! I
> understand that I can't simply re-run Heat on every build - I have to
> check in the file it generates into revision control so that the GUIDs
> it assigns are kept - but obviously I'd prefer to automate whatever I can.
>
> Any help that anyone can offer would be gratefully received. If there's
> a "hello world" project out there that uses WiX and Heat in the
> recommended way, that would help me a lot. Thanks!
> --
> [][][] Paul Crowley
> [][] LShift Ltd
> [] [] www.lshift.net
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> WiX-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
