VB utilities??

  • Thread starter Thread starter Don
  • Start date Start date
D

Don

The compamy that I was doing software development went bust in early
2001 and I've only occasionally been messin' arround with programming
since.

On one of my attempts to get into VB.Net I think I saw a free add-in
that did a "sort-of" stack trace of all your code. It went threw all
the code modules and built a heirarchy of what procedure called what
others. It also found dead procs. It was like that Aivosto add-in for
VB5 & 6.

Am I making sense? Does anyone have a clue abouy waht I'm talking
about?

Any help will be appreciated.

Don
 
Don,

I think it does not make sense. Partially your code is done from the stack,
however a much more major part is done from the objects, which are instanced
and released all the times. Some thousands time in a nanosecond.

Just my two worthless Dutch cents.

Cor
 
Aren't they Euro Cents these days?

Cor Ligthert said:
Don,

I think it does not make sense. Partially your code is done from the
stack, however a much more major part is done from the objects, which are
instanced and released all the times. Some thousands time in a nanosecond.

Just my two worthless Dutch cents.

Cor
Click to expand...
 
Hi Cor,

Yes, I understand how the "actual" call stack works. What I'm talking
about is an add-in that builds a hierarchical list of procedure calls.
It's for a number of purposes, 1. to find dead procedures that are
never called. 2. to illustrate how the application is designed. It's a
bit like the idea of a flowchart. I know that a flowchart can not
anticipate how an event driven app will actually run though.

The Aivosto add-in that I mentioned had this function (among many
others). I found it quite helpful in understanding how someone else's
software works.

http://www.aivosto.com/

Thank you for your help,

Don
 
Don,

From your message I understand that you know how the stacks work. However
what do you do with all the objects. Those are not in the stack and have a
lot of hidden codes.

By the way, the program you are talking about are in my idea already there.

Have a look at google for "profiler Net"

I hope this gives an idea

Cor
 
Hello Cor,

I'm sorry, I should not have used the word "stack". What I was trying
to say, but did not do a very good job of, was something like below.

Thank you,
Don

Sub Main
Sub3
End Sub

Sub Sub2
Sub4
End Sub

Sub Sub3
Sub2
End Sub

Sub Sub4
'--Do Something
End Sub

Function Func1
Sub2
End Function

Function Func2
'--Do Something else
End Function

* * * OUTPUT * * *
Main
----Sub3
--------Sub2
------------Sub4

Func1
----Sub2

DEAD PROCEDURES

Function Func2

DECLARED but UNUSED VARIABLES

mstrDbPath As String, Declared in Sub3
mintParent As Intege, Declared in Func7
 
Don,

I understood that, however what as it is this

Sub1

dim a as classA
a.methoda
all other methods of objecta are not used.


in a.methoda
dim b as classB
b.methodb
all other methods of methodb are not used.

etc.

End sub

The way you show it is not the way as it is done in VBNet anymore. That is
the main difference between VB<7 and dotnet VB.

Cor
 
DEAD PROCEDURES
Function Func2

DECLARED but UNUSED VARIABLES

mstrDbPath As String, Declared in Sub3
mintParent As Intege, Declared in Func7
Click to expand...

You can use MZ-Tools add-in (http://www.mztools.com/) to review dead
code. It does exactly what you described above.

In addition, it doesn't show method call "stack" but it has similar very
useful function "Find Method Callers".
 
Back
Top