Call Hierarchy

  • Thread starter Thread starter Chris Botha
  • Start date Start date
C

Chris Botha

I need the call hierarchy of procedures in a project in order to trace the
calling path of procedures.
I googled and found this nifty functionality is included in VS 2010, but I
can't wait, I kind of need this right now.

Anyone knows of something available?
I'm using VS 2008 and the project is a VB .net project.

Thanks.
 
Chris Botha said:
I need the call hierarchy of procedures in a project in order to trace the
calling path of procedures.
I googled and found this nifty functionality is included in VS 2010, but I
can't wait, I kind of need this right now.

Anyone knows of something available?
I'm using VS 2008 and the project is a VB .net project.

I'm not sure if this is what you are looking for but...

One solution is to set a breakpoint in the beginning of the Sub or Function.
When your program hits the breakpoint you can see the call stack in VB
(press Ctrl+L if it's not in sight).

-Teemu
 
Chris Botha said:
I need the call hierarchy of procedures in a project in order to trace the
calling path of procedures.
I googled and found this nifty functionality is included in VS 2010, but I
can't wait, I kind of need this right now.

Anyone knows of something available?
I'm using VS 2008 and the project is a VB .net project.

Thanks.


You could add logging information at the start of every routine (tedious, I
know...).

Something like this could be added:

Console.Out.WriteLine(new StackTrace().ToString());
 
Thanks, it is a big project in production, probably close to a thousand
functions and numerous paths to the function I am interested in, so I need
some kind of a tool to give me the call hierarchy so that I can back-track
the call paths.
 
I need the call hierarchy of procedures in a project in order to trace the
calling path of procedures.
I googled and found this nifty functionality is included in VS 2010, but I
can't wait, I kind of need this right now.

Anyone knows of something available?
I'm using VS 2008 and the project is a VB .net project.

Thanks.

Hi Chris,

Previously suggested methods are the best practices as I know. However
you wrote, as its big project, it is not feasiable. I am curious to
know the purpose behind knowing the calling hierarchy. Is it for the
sake of reverse engineering some maintainency project or for dynamic
analysis / code coverage of new project .... The suggestion will
differ depending on the situation.


Thanks
-Cnu
 
Reflector lets you do that but only one method at a time rather than
auto-processing all methods and outputting the result to a report.
 
Back
Top