Matt Watson

Thanks for the link Dependency Walker. I used it to solve a problem that had been haunting me for ages. -- David

Looks neat, but didn't work with my .Net dll.

To get the dependancies for a .Net assembly you can just use ildasm: http://msdn2.microsoft.com/en-us/library/f7dy01k1(VS.80).aspx

I've blogged about it here: http://devproj20.blogspot.com/2007/11/dll-dependencies.html

can i use this tool to get rid of unused dlls left behind as shared dlls after uninstalling prorams?
i recently aquired a pc from someone who left 14 software programs, messaging programs, ftp programs and various other utilities on it. when i got it home i proceeded to uninstall everything but windows opting not to remove shared dlls in fear of having problems when i was done removing things that i didnt want.
i have fished through the registry removing references to those programs i removed and went into the startup utility to check that too.
i know for a fact that there are lots of useless dlls on my harddrive and DO NOT want to make a note of last used and last modified dates for every dll,, run the remaining programs and retake the used and modified info to find out which dlls are just there dead and taking up space.

>I've blogged about it here:

barely!!

you mentioned it!!

waste of everyones time!!

tell me some s/w to read the .dll files of driver

Nice, just what I was looking for !