Richard, my old blog has the entry you're thinking of:
http://blogs.msdn.com/robmen/archive/2003/10/18/56497.aspx
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, September 13, 2007 05:15
To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] telling WiX to get files from Team Foundation Server
Peter,
If Heat is exiting with an ArgumentNullException it seems likely that you have
caught a bug. I suggest making sure it is added to the tracker (at
http://sourceforge.net/tracker/?atid=642714&group_id=105970&func=browse - I
haven't checked to see if there is one entered already).
WiX is really not good (at least not yet) in scenarios where there are large
numbers of arbitrarily changing files. This is an intentional design decision
due to the Microsoft Installer component rules, and the difficulties associated
with creating component definitions which are easy to service (apply patches
to, etc). IGNORE THE COMPONENT RULES AT YOUR OWN RISK! I thought Rob's blog
(http://robmensching.com/blog/) had quite a lot of details behind this
decision, and some examples of what could get messed up if the component rules
are ignored but it appears I was wrong. Having said that, you may want to read
http://robmensching.com/blog/archive/2007/03/09/Windows-Installer-identifiers-must-be-stable.aspx,
and the pages it links to.
The best mechanism, but as you have observed not an automated one, is to
educate your developers so they know that when they add a file to the solution
they also need to add a reference to the WiX source if the file needs to be
deployed. Sadly, in many (if not most) large team environments developers don't
concern themselves with setup.
Sorry I can't help with your immediate problem.
Regards,
Richard
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, September 13, 2007 6:49 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] telling WiX to get files from Team Foundation Server
Hi WiX-Team,
I am new to WiX and testing it for about a week, because we need to customize
the standard Setup of Visual Studio for our webapplication. The problem is that
we got a pretty big webapplication (about 3000 files and 200 folders to deploy)
and we are using VS 2005 with Team Foundation Server. So here is the problem
concerning WiX, I was not able to find any solution in WiX to told it to get
every File of the Repository folder (especially new checked-in files), the only
thing I found was to write to the wxs the folderstructure and then adding the
files, but it is really time consuming to do this and its not really an
autobuild. Also heat was not able to create a wxs file for me because it does
always exit with a System.ArgumentNullException. If I decompile the setup of
Visual Studio with dark it creates me a 2MB wxs file with no real structure at
all. So is there a possibility to solve this case, or perhaps is there some
kind of workaround or other technology that could help me out, because I do not
find a post in the mailing list concerning this problem (or perhaps I was only
not able to find it)
Regards,
Peter Huster
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
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