[Message Deleted]
-
If the dll is not loaded into memory then it's not being used. However, you probably mean "how many programs might potentially need the dll if and when they are run". The answer is there's not really any way to tell. You could run the
dependstool on all the executables on the computer but you still wouldn't know because the dll might be loaded at run-time by something. Shared dll's are supposed to be registered so they appear in the registry but there's nothing to guarantee that. The only way to be sure is to delete the dll and then run absolutely every application using every possible feature under every possible condition. If something complains then the dll was needed. If not then it (probably) wasn't.
The opinions expressed in this communication do not necessarily represent those of the author (especially if you find them impolite, discourteous or inflammatory).
-
You could use the windows search for files option to find *.exe and *.dll files that contain the name of the dll in question -- Help me! I'm turning into a grapefruit! Phoenix Paint - back from DPaint's ashes!
-
You could use the windows search for files option to find *.exe and *.dll files that contain the name of the dll in question -- Help me! I'm turning into a grapefruit! Phoenix Paint - back from DPaint's ashes!
benjymous wrote: You could use the windows search for files option to find *.exe and *.dll files that contain the name of the dll in question This is no better than using the depends tool. It does not take account of the possibility of programs loading dll's at runtime. The name of the dll may be built at runtime from user input or registry/ini settings for example.
The opinions expressed in this communication do not necessarily represent those of the author (especially if you find them impolite, discourteous or inflammatory).