The con of this is that you’ll include files that you otherwise might not want to. By always recreating the whole fragment you don’t have to worry about missing any new files you add.
#WIX FORMATTED FILE IDENTIFIER PRO#
The con is that you have to do the pro part by hand. The pro of this is that you can add or remove components by hand.
You might ask what harvesting means? Harvesting is converting a source (file, directory, …) into a component structure saved in a WiX fragment (a wxs) file. Heat is a command line utility to harvest a file, directory, Visual Studio project, IIS website or performance counters. What we need is an automated way to create this structure. Writing a directory structure for so many files by hand is out of the question. It all depends on what kind of application you’re building. But in the real world we have 10s or 100s of different files from dll’s to resource files like pictures. For our SuperForm application we have a single exe to install.
#WIX FORMATTED FILE IDENTIFIER HOW TO#
In this post I’ll show you how to automate inclusion of files to install into your build process.
In previous posts I’ve shown you our SuperForm test application solution structure and how the main wxs and wxi include file look like. WiX 3 Tutorial: Generating file/directory fragments with Heat.exe
0 kommentar(er)
