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 > ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding 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 ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding 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
