I have a project with some C# dlls that use other vb6 dlls. I also have vb6 dlls that use other vb6 dlls. I would like to map all these dependencies, so I’ll know which vb6 dlls are still used.
Thanks.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a project with some C# dlls that use other vb6 dlls. I also have vb6 dlls that use other vb6 dlls. I would like to map all these dependencies, so I’ll know which vb6 dlls are still used.
Thanks.
You take a piece of paper and write on it the name of all your DLLs. Then you take a pen and draw an arrow from DLL A to DLL B if DLL A has a dependency on DLL B.
After that, you know that a DLL is unused if there are no arrows pointing towards it.
What you have now is a directed acyclic graph (DAG) — it’s probably not a tree, since you might have a DLL A that references DLLs B and C, both of which reference DLL D.
Since every DAG induces a partial order, you can take a fresh piece of paper and redraw your graph such that the DLLs that are dependencies are below the DLLs which have them as dependencies, which will make a useful reference sheet.