Adam Kennedy-3 wrote:
>
> I'm trying to write an .msi target (zip and eve targets already exist)
> for a project that I do not myself control (The Perl programming
> language) and that changes over time.
>
> This rules out the recommended approach of hand-crafting the Wix XML
> files at the same time as the code is written, because I can't do that.
>
> That means I have no choice but to dynamically generate the Wix XML from
> a set of files.
>
Hi Adam,
one point to look might be the enhanced tallow tool named 'mallow' which is
inteded to create consistent guids on subsequent calls. But both are
designed for Wix 2.0 only.
My suggestion is following:
- Use heat (v3.0) to crawl your directories as your starting point
- Adjust all entries to your needs
- When it comes to an upgrade then just run wix, do an administrative
install an compare this directory with your base one. As result you will get
a list which files are missing in install. (Wix will show obsolete files)
- This missing files then must be added to your wxs files (which should not
be a issue since you might use perl)
for comparing the install to your base see
http://www.nabble.com/Wix-layout-td12592040.html for a batch and a nant
solution.
hth
Dominik
--
View this message in context:
http://www.nabble.com/A-set-of-incrementally-more-complex-examples-to-help-writing-build-automation-tp15241530p15268199.html
Sent from the wix-users mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
