Tracking what dlls/ocxs an app loads?
- From: "cada0310" <cada0310@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 27 Jun 2005 11:50:02 -0700
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
.
- Follow-Ups:
- Re: Tracking what dlls/ocxs an app loads?
- From: Arnie
- Re: Tracking what dlls/ocxs an app loads?
- From: David Lowndes
- Re: Tracking what dlls/ocxs an app loads?
- Prev by Date: Profiler for VC++ 6.0 (Standard)
- Next by Date: Re: Tracking what dlls/ocxs an app loads?
- Previous by thread: Profiler for VC++ 6.0 (Standard)
- Next by thread: Re: Tracking what dlls/ocxs an app loads?
- Index(es):
Relevant Pages
|