Thanks for reply to all who answered. I would try to summarize.
1. The features of dependency detection (as seen in InstallShiled and Package and Deployment projects) are not part of the WiX toolkit. There is no way to generate any .wxs source that can be used in the installer neither with WiX toolkit nor any additional tool like Votive or others. 2. This dependency detection is error-prone and cannot really automated. 3. You have seen in large projects, that it is essential to manually compose an installation. It's easy to follow the patterns and reduce the effort. Thanks guys, I will try to promote my little experience with WiX and this help to my colleagues. Below you see the usual wishes that clearly are induced by other installer generators. Regards, Helge Am 16.05.2011 21:26, schrieb Castro, Edwin G. (Hillsboro): > What is the list of "runtime" dependencies that will be detected by the > feature? The list has one item: The redistributable MSCVRT in the correct version. This version is identified with the embedded manifest. > More importantly what should be done in response to such a detection? Install the MSM. > Should the feature generate a launch condition to fail the installation? No, the MSVCRT binaries shall be installed smoothly. > Should the feature generate code to automatically download and install the > missing runtime? No, the existing MSM should be included in the MSI. > Should the feature generate code to automatically install the runtime from a > bundled installer package? > If the dependent runtime installer is bundled then does the WiX toolset > bundle these packages in the WiX toolset itself? (I suspect we'd get a very > big "Heck NO!" from most of the maintainers...) > > This feature would only be as useful as the information needed to generate > the code above remains current *and* it provides enough options for a setup > engineer to decide what to do. > > Seems to me that the WiX community could provide value by posting the > information needed to detect common runtimes and other third party tools and > libraries on a wiki of some kind. I don't think we need a tool to > automatically detect our dependencies as we should be aware what those > dependencies are. Such a wiki could also contain examples of how to react > when a dependency is not installed on the target system. I guess I see this > as a WiX Cookbook Wiki. > > Edwin G. Castro > Software Developer - Staff > Digital Channels > Fiserv > Office: 503-746-0643 > Fax: 503-617-0291 > www.fiserv.com > Please consider the environment before printing this e-mail > > >> -----Original Message----- >> From: Helge Kruse [mailto:helge.kruse-nos...@gmx.net] >> Sent: Monday, May 16, 2011 11:45 AM >> To: wix-users@lists.sourceforge.net >> Subject: Re: [WiX-users] Detection of run-time DLLs >> >> So you would say, it's impossible with the Windows Installer XML tool set? Or >> is it possible but insane? >> >> >> Am 16.05.2011 20:14, schrieb Christopher Painter: >>> I maintain installers that rival Visual Studio in terms of size and >>> complexity. >> Factoring dependency relationships is critical and cannot be automated. >> I've >> streamlined the process to the point that it's insanely fast and easy to >> follow >> the established patterns but it still takes a human to apply domain and >> engineering knowledge to make the right call. >>> >>> --- >>> Christopher Painter, Author of Deployment Engineering Blog >>> Have a hot tip, know a secret or read a really good thread that deserves >> attention? E-Mail Me >>> >>> --- On Mon, 5/16/11, Helge Kruse<helge.kruse-nos...@gmx.net> wrote: >>> >>> >>> From: Helge Kruse<helge.kruse-nos...@gmx.net> >>> Subject: Re: [WiX-users] Detection of run-time DLLs >>> To: wix-users@lists.sourceforge.net >>> Date: Monday, May 16, 2011, 11:47 AM >>> >>> >>> >>> Am 16.05.2011 17:53, schrieb Christopher Painter: >>>> To be honest, that's not a "feature" of InstallShield that I like or use. >> Magically "Easy" buttons are a great concept but I don't like switching off >> my >> brain. >>>> >>> >>> Yea, maybe. But it's not necessary to switch off any brain, when such a >>> dependency is detected. I think the HEAT tool would be a good candidate, >>> since it generates a .wxs file that should be edited manually. >>> >>> The great benefit of such feature is that you don't create a MSI file >>> that installs a product on your development PC but does not run on a >>> system where this run-times are not installed. >>> >>> Helge >>> >>>> >>>> --- >>>> Christopher Painter, Author of Deployment Engineering Blog >>>> Have a hot tip, know a secret or read a really good thread that deserves >> attention? E-Mail Me >>>> >>>> --- On Mon, 5/16/11, Helge Kruse<helge.kruse-nos...@gmx.net> >> wrote: >>>> >>>> >>>> From: Helge Kruse<helge.kruse-nos...@gmx.net> >>>> Subject: [WiX-users] Detection of run-time DLLs >>>> To: wix-users@lists.sourceforge.net >>>> Date: Monday, May 16, 2011, 10:24 AM >>>> >>>> >>>> Hello, >>>> >>>> I know from InstallShield (IS) that it is capable to detect all the >> dependencies of a binary to run-time DLLs. >>>> >>>> When VS2005 C++ DLL uses the msvcrt IS adds the corresponding MSM to >> the project. How can do similar with WiX 3.5? It would includ this tasks: >>>> >>>> - detect automagically which run-time DLLs are necessary >>>> - add these run-times conviniently >>>> - keep track of updates to these run-times as it happens when VS2005SP1 >> or the lastest April update of VS2005 changes the versions, that are used in >> VS2005 when linking a DLL? >>>> >>>> The last point means, I want only to recompile the installer with WiX to >>>> get >> the current dependencies included. >>>> >>>> I tried to evaluate the HEAT options but did not found any appropriate. >>>> >>>> Regards, >>>> Helge >>>> ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
