#6 Restricting profiler to specific methods and Call Graphs

[Anonymous]

Is there any way to restrict profiler to specific methods?
Right now one can exclude certain namespaces after
the program has finished execution but if the profiler can
be restricted to perform timing calculations for specific
methods/classes/namespaces it might speed up the
task of profiling in complex projects. An idea for doing
this would be to use attributes to mark
methods/classes/namespaces for profiling (like
HarnessIt does for unit testing). If this cannot be done
by the current GUI then is there provision in the API to
handle it; so basically someone who wants this feature
can do so himself?

Another feature thats worth having is a Call Graph (see
DevPartner or VB Watch 2 Protector); a way of
depicting the flow of control from one method to another.
This, I assume, is possible to code externally if needed.
But, if there is future plan for this then let me know.

ahmad.kabani@unitron.com