Re: Tracking what dlls/ocxs an app loads?
- From: "Arnie" <none>
- Date: Tue, 28 Jun 2005 12:06:08 -0400
"cada0310" <cada0310@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6F092E5B-D666-45E5-8852-1B12132FEB1A@xxxxxxxxxxxxxxxx
> Hi there,
>
> Is there a way to somehow trap the paths of the modules that an
> application
> loads at runtime, for a release executeable? Something like
> what displays in
> the Output window of the .NET IDE when you start up an
> application?
>
> I'd like to get that path, then get the version information for
> the
> dll/whatever and store it in our log file.
>
> Thanks for any help you can provide,
>
> Chris
Hi Chris. There is a console utility called listdlls.exe that
will output the path and version information for everything.
It's free. I suppose you could run it via CreateProcess,
redirecting stdout to a file and then read the file.
However, it soulds like you would probably be happier with the
'guts' of listdlls. In any case, here's a link:
http://www.sysinternals.com/Utilities/ListDlls.html
- Arnie
.
- References:
- Tracking what dlls/ocxs an app loads?
- From: cada0310
- Tracking what dlls/ocxs an app loads?
- Prev by Date: Re: Tracking what dlls/ocxs an app loads?
- Next by Date: _int64 or __int64
- Previous by thread: Re: Tracking what dlls/ocxs an app loads?
- Next by thread: _int64 or __int64
- Index(es):
Relevant Pages
|