Just curious where people are with this. I've re-visited this for the first time in a while. It seems to me the options now are:
1) Installshield Pro: Commercially Supported Project - large user/support base, MSBuild Based Con: Free Version very limited - otherwise costs 2) Visual Studio Setup Project Pro: Free, part of Visual Studio Con: Deprecated (Going away in Dev 11) Not MSBuild based - so requires Visual Studio to be installed on the Build server, hack to run etc 3) WIX Pro: Very Powerful, well supported Open Source Con: Steep learning Curve, I just started looking at WIX and the one thing I REALLY didn't like. Evidently the "HEAT" tool that "harvests" project file for content files, resource, binary output etc doesn't "honor" the Assembly Reference for a project to get the DLL's. It seems to me you either need to expliclity list all the DLL's you want in your deployment manually (and need to update the configuration every time you add an assembly - including project references) or do what looked like a "hack" to me with tweaking the command line for HEAT and doing an XSLT to get them. Am I missing something? Are there other options? What are the members of the list here using to create MSI's from Team Build? Thanks Dan Daniel Sniderman | Senior Consultant - Midwest Region | MCSD.Net, MCTS: Team Foundation Server 333 E. Butterfield Rd, Suite 100, Lombard, IL 60148 * Cell: 847,668,4882 |*eFax: 847.390.7810 [cid:[email protected]]
<<inline: image001.jpg>>
_______________________________________________ oztfs mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/oztfs
