Runtime Flow blog (Understanding a control flow in a running .NET application)

Runtime Flow v1.2.2 released – fixed an unhandled exception for solutions with unloaded projects.

Runtime Flow v1.2.1 released – added the portable edition, added browse buttons to the Customized run dialog, added the E-mail support button to the toolbar.

I’ve created the portable Runtime Flow edition that can work without Visual Studio and almost without installation. It should be perfect for troubleshooting problems after deployment. The main window contains the toolbar that performs exactly the same functions as the toolbar integrated with Visual Studio:

Runtime Flow portable edition

You can download the portable edition as a zip archive containing following files:

Runtime Flow portable files

The only installation step required is profiler COM class registration. If you don’t have admin rights and you only need to monitor applications under the current account, run “Register profiler for the current user.cmd”. If you have admin rights, it is recommended to run “Register profiler for the local machine.cmd”. When no longer needed, you can unregister the profiler with the appropriate “Unregister…” script.

Runtime Flow portable requires .NET 3.5 SP1 to be installed (or .NET 3.0 plus VS 2008 C++ runtime) when running on Windows XP and Vista. On Windows 7 no additional components required.

Download link: Runtime Flow portable v1.2.1.

Runtime Flow v1.2.0 released:

• added persistence for monitoring options and customized run settings,
• added the Copy as text command to the Flow and Summary windows,
• added target window opening if it was hidden on the locate in other window command,
• added function return type for tail calls,
• changed parenthesis around object data to curly braces,
• disabled filter buttons when empty class name is selected in the Summary window,
• fixed filter expression for functions with empty class name,
• fixed not visible tooltips for floating windows.