Get the latest Arbed beta first (it's some 1.7.0 beta).
Next to the Arbed.exe there's a Scripts folder.
There should be a "Add DebugLog to all methods.arbs" in there.
Open both that script and your project in Arbed. (Make sure you have a backup of your project, e.g. stored in Version Control, because once you modify your project with this procedure, it'll be not so easy to remove the changes again, because there's no script for that, yet, unless you write your own).
The script is set up to add
to all your methods, logging every method entry.
You could modify the script to invoke
dim myTmpObject as new MethodProfiler(CurrentMethodName)
instead, to get both method entries and exits logged.
If you want to use the MethodProfiler, I suggest changing the following script line:
textToAddToTopOfSource = "System.DebugLog CurrentMethodName" + EndOfLine
textToAddToTopOfSource = "#if DebugBuild" + EndOfLine + "dim myTmpObject as new MethodProfiler(CurrentMethodName)" + EndOfLine + "#endif" + EndOfLine + EndOfLine
Then run the script and verify that your methods have gotten the intended line added.
Save the project and run it in the IDE. If you added the line with "MethodProfiler", you will also have to add this MethodProfiler class to your project, of course. That class can be found in the demo project, see my blog article .
Now, if your modified project runs, it'll write lots of log messages to the system console. which can be viewed with the "Console.app" on the Mac, or with the "DebugView" tool (google for that) on Windows. In case of Windows, you'll have to launch DebugView before you run the program in the IDE.