I have a really large solution S
with several projects, dll
s, etc.
I need to document which classes and methods from one dll D
(which we have writen, it ia our dll with source code, almost ~500 functions) are actually used within a solution S
, so that I can get in my doc only functions that are actually used.
Is there any program/hack/solution to such a problem? Because 500 seems to be a large number, and using "Find <function name> in entire solution"
manually seems hell to me.
Any ideas? How can I get some kind of debug info
?
We are using MCVS 2010
You could remove the library D
from the linking step and see how many unresolved external symbols you have. This would leave only functions defined in headers which you have to check by hand.
You could also see the library (if it exists) generated by S
or its projects - most lib's have an import table which is a list of functions imported from other modules.
However, the issue here seems to be in the design of D
. The public interface should be fully documented, but shouldn't expose what isn't necessary (no internal functions, no internal functionality). If it was like this, you wouldn't have this problem.