Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, March 7, 2019 10:28 AM | 1 vote
Probably any developer working with windows knows about the dependency walker (depends.exe)
The sad situation is that this very useful program has not been updated in quite a while and has some issues that make it almost unusable in modern windows.
I have recently contacted the original author of depends.exe, Steve Miller offering to make the necessary updates to the code base and release a new version. His reply was that since this program is something he worked on when he was an MS employee, it is probably owned by MS, so he doesn't know what can be done.
I'd like to get the contact information for the right person in MS to talk to about things like this with the eventual goal of open sourcing this utility and being able to create an updated release.
Who do I talk with to make this happen?
All replies (4)
Thursday, March 7, 2019 4:01 PM
Probably any developer working with windows knows about the dependency walker (depends.exe)
The sad situation is that this very useful program has not been updated in quite a while and has some issues that make it almost unusable in modern windows.
I have recently contacted the original author of depends.exe, Steve Miller offering to make the necessary updates to the code base and release a new version. His reply was that since this program is something he worked on when he was an MS employee, it is probably owned by MS, so he doesn't know what can be done.
I'd like to get the contact information for the right person in MS to talk to about things like this with the eventual goal of open sourcing this utility and being able to create an updated release.Who do I talk with to make this happen?
It can't be too hard to design something like this from scratch and make it open source, how about beginning by creating a list of key requirements?
I also asked the .Net Core team to consider improving the assembly load failure exception because that is very unhelpful and just states "Could not load file or assembly 'WHATEVER.DLL' or one of its dependencies".
In reality this should be described a bit like a stack trace, because you'll get the same exception if WHATEVER.DLL isn't found or something used by WHATEVER.DLL. When we get this exception its frustrating and time consuming to find out exactly what missing yet expected file led to the load failing.
I'd be interested in starting this.
Friday, March 8, 2019 8:57 AM
Hi friend,
Welcome to MSDN forum.
The development of dependency walker has stopped around 2006. We recommend you using dependencies. It is a rewrite of dependency walker, and also can troubleshooting dll load dependencies issue.
Thank you for understanding and sorry for this inconvenience.
Best Regards,
Dylan
MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]
Friday, March 8, 2019 11:30 AM | 1 vote
>The development of dependency walker has stopped around 2006. We recommend you usingdependencies <https://github.com/lucasg/Dependencies>. It is a rewrite of dependency walker, and also can troubleshooting dll load dependencies issue.
Thanks for mentioning it Dylan, I've not heard of it before.
Dave
Thursday, March 14, 2019 7:02 AM
hi David,
Thank you for your reply. You are welcome.
Regards,
Dylan
MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]