Use Process viewer that ships with Visual Studio and/or C++. It allows you
to browse through a tree like interface of dependencies for any executable
file (dll, ocx, exe, etc.). It also shows dependencies of dependencies.
Although PView will show you dependencies all the down to the OS core files,
I really advise that you dont ship Kernel32.dll.

Matthew A. Overlund

John McLaughlin <johnm@oei.com> wrote in message
news:38a751f5@news.dev-archive.com...
> InstallShield? I am using Wise InstallBuilder. I assume they are
> equivalent.
>
> My question relates to identifying the files that need to be added to an
> install package. What run-time elements are needed beyond your own files
> need to be included? How do we determine this? The installer can then
> decide if, for example, MSVCRT.DLL needs to be actually installed at
> "install time" based on version or date/time or ... But where are the
> run-time dependencies documented? For example, how do I know if I need:
> oleaut32.dll,
> olepro32.dll,
> Msvbvm60.dll,
> Msstdfmt.dll,
> etc...
>
> There are utilities that can monitor an EXE to see which DLL's it loads,
but
> I have found this to be incomplete, for example in the case of it loading
a
> COM local-server (EXE).
>
> I have trouble believing this process is so "trial-and-error" based.
Anyone
> have some direction for this issue?
>
> John
>
> --
> _______________________
> John McLaughlin
> johnm@oei.com
>
> Bill Heffner <bill@sonora-sw.com> wrote in message
> news:38a5790a@news.dev-archive.com...
> >
> > "John McLaughlin" <johnm@oei.com> wrote:
> > >Am I missing something? I am trying to create another SETUP.EXE and I
am
> > >looking for some wisdom.
> > >
> > >Trying to get all the required run-time files for an application that
> > >consists of :
> > > VB EXE's (GUI apps),
> > > VB COM DLL's (in-proc COM server),
> > > C++ EXE's,
> > > C++ COM DLL's (in-proc COM server),
> > > C++ COM EXE's (local COM server),
> > > C++ non-COM DLL's (plain old DLL's)
> > >seems to be one of:
> > >
> > >1. Make an install package
> > >2. Try installing on a virgin target machine
> > >3. Test the app
> > >4. Figure out what is missing if something doesn't and add it to the
> install
> > >package script
> > >5. Make the target machine virgin again (restore disk image)
> > >5. Go back to #1
> > >
> > >...and repeat until everything works.
> > >
> > >Isn't there a more formal or scientific way to identify what is needed
at
> > >run-time?
> > >
> > >John
> > >
> > >
> > >--
> > >_______________________
> > >John McLaughlin
> > >johnm@oei.com
> > >
> > >
> > >
> > InstallShield
>
>