Hello, What is the best practice for dealing with shared binaries like .NET assemblies or DLL's?
If I have some number of VS projects that each output a a COMMON.DLL to their respective bin\Release folder, how can WiX know which COMMON.DLL is the latest version? Does WiX have any features similar to the VS installer, where you can add the output of a project in the solution to the build process? I have already used heat to create wxs files for legacy VB applications. Is heat also the right tool to use for .NET applications as well? If this is all well documented somewhere, please point me in the right direction. If all of this is covered in the tutorial, I seem to have missed it. Thanks, Bill McCormick -- ACE-CO 5355 Dietrich Rd. San Antonio, TX 78219 (210) 661-4111 x512 (800) 676-4111 Toll Free (210) 662-6177 Fax (210) 216-6641 Cell mailto:wpmccorm...@ace-co.com http://www.ace-co.com ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
