When I generate wxs sources using heat I treat it as a build product. I do not keep the generated file in source control. I dynamically add the generated file to the ItemGroup that contains the wxs source files to compile. An ItemGroup is similar in concept to a fileset in NAnt.
I personally believe that tagging should be performed _after_ a successful build especially when you have a source control system that only allows atomic commits (such as subversion). You can always track back to the specific commit you checked out and tag that specific commit upon successful builds if you need a different way to refer to the source code used in a particular build... but that's unrelated to WiX so I'll just leave it at that. If you guys decide that heat generation is consistent enough for your purposes then I would simply recommend that you do not keep the generated wxs source in source control as it really is a build product. As long as the contents of the directory that is getting harvested can be reproduced exactly then you can generate the corresponding wxs source correctly. 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: Beth Hechanova [mailto:bhechan...@imsco-us.com] > Sent: Wednesday, July 07, 2010 10:13 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Recursively install directory and subdirs/files toa > folder > > My automated build uses cruisecontrol.net, nant, and candle/light to build my > installer via the .wxs file. I do not have a .wixproj file. My application > has two different installs - one for the application code (executable, dlls), > which will be used by all customers. The other installer is not the > application code, but miscellaneous files (docs, icons/images, configuration > data, and perhaps other applications) - this is customer specific. Right now, > we manage all this customer specific data, but outside the realm of our > application, so it has a separate installer. > > The short answer on the build scheme is prior to a build, all source (this > includes the .wxs file) is tagged (svn is our source control), then extracted > to a new directory for the build. If our build dynamically generates the wxs > file, then it is no longer a static source file to be tagged at the beginning > of the build, but instead more of a build product. This might be ok, I just > have to determine if this is what we want to do. The goal is to be able to > recreate the build products at any time from our source control for a given > version, so as long as that goal is met, perhaps we don't need to specifically > tag the wxs file. > > But it seems like we wouldn't want a mixture of specifying some files in the > wxs file, and dynamically generating others. I don't really know too much > about heat - I just tried a quick test as I found references to using it to do > what I want. > > I'm wondering though if this data (at least some of it), belongs in an > installer. At least for the document tree, upon an uninstall, we want to > remove the root directory and everything below, regardless of whether or not > it was contained in the original install. This may seem incorrect, but those > are the requirements. > > From a previous post, it does not seem like this is possible, at least via the > .wxs file - I need to use heat to generate the file list, or copy these files > outside of using wix. > > Thanks, > Beth > > -----Original Message----- > From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] > Sent: Wednesday, July 07, 2010 9:44 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Recursively install directory and subdirs/files toa > folder > > > -----Original Message----- > > From: Beth Hechanova [mailto:bhechan...@imsco-us.com] > > > > I found a few references to using heat. I tried that out, which seems to > > generate a wxs fragment with the proper list of files and subdirs. So > perhaps > > that can be integrated into my automated build, but how are builds are > setup, > > using heat doesn't quite fit into our scheme. > > What is your scheme? > > I use heat all the time by simply integrating its use directly into the > *.wixproj file since it's just a MSBuild file. I typically override the > BeforeCompileAndLink target and use the HeatDirectory task provided by WiX. > Unfortunately, the HeatDirectory task is not documented so I usually use > reflector to determine what the available properties are. > > If you can provide some details of your build scheme then I can try to help > automate the execution of heat in your scheme. > > 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 > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > --------------------------------------------------------------------------- > This email and any files transmitted with it are confidential & proprietary to > Systems and > Software Enterprises, Inc. (dba IMS). This information is intended solely for > the use of > the individual or entity to which it is addressed. Access or transmittal of > the information > contained in this e-mail, in full or in part, to any other organization or > persons is not > authorized. > --------------------------------------------------------------------------- > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
