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

January 11, 2017

Visual Studio 2017 support

Filed under: Uncategorized — Sergey Vlasov @ 1:02 pm

I’ve created a Visual Studio 2017 integration module for Runtime Flow that should be installed along with the main installer.

Download link: RuntimeFlow2017.vsix.

June 20, 2016

Runtime Flow v1.6.0 released

Filed under: Uncategorized — Sergey Vlasov @ 5:48 pm

Runtime Flow v1.6.0 released:

  • Added the ability to save and open monitoring results.
  • Created an API for programmatic access to saved and real time monitoring data.
  • Improved monitoring performance up to 30%.
  • Added the parent class name to internal classes.
  • Stopped support for Visual Studio 2008/2005.
  • Stopped support for the portable edition running with .NET 3.5.

Download links: Visual Studio edition, Portable edition.

June 16, 2015

Runtime Flow v1.5.1 released

Filed under: Uncategorized — Sergey Vlasov @ 3:42 pm

Runtime Flow v1.5.1 released: Fixed incorrect monitoring started for an auxiliary process when it was launched by the main target executable.

Download links: Visual Studio edition, Portable edition.

June 3, 2015

Runtime Flow v1.5.0 released

Filed under: Uncategorized — Sergey Vlasov @ 1:12 pm

Runtime Flow v1.5.0 released: added support for Visual Studio 2015 and fixed the “Output file name required for the Start Project option” error when starting monitoring in a localized Visual Studio edition.

Download the Visual Studio edition.

October 15, 2013

Runtime Flow v1.3.5 released

Filed under: Uncategorized — Sergey Vlasov @ 6:52 am

Runtime Flow v1.3.5 released: added support for Visual Studio 2013 and added the ability to run without .NET 3 installed in Visual Studio 2010+.

Download link: Visual Studio edition.

September 6, 2012

Runtime Flow v1.3.4 released

Filed under: Uncategorized — Sergey Vlasov @ 6:10 am

Runtime Flow v1.3.4 released: fixed a problem with Visual Studio 2012 registration on 64bit Windows.

Download link: Visual Studio edition.

June 12, 2012

Runtime Flow v1.3.3 released

Filed under: Uncategorized — Sergey Vlasov @ 3:41 pm

Runtime Flow v1.3.3 released: added support for Visual Studio 2012 RC.

Download link: Visual Studio edition.

January 19, 2012

Monitoring a .NET application running in IIS

Filed under: Uncategorized — Sergey Vlasov @ 2:27 am

Runtime Flow can monitor a .NET application running in IIS, but currently it requires manual configuration and only one IIS worker process (w3wp.exe) can be monitored. Below are the steps I used to monitor a sample ASP.NET MVC2 application configured to use local IIS Web server, created in Visual Studio 2010 and running on Windows 7:

A sample MVC application in Visual Studio 2010 configured to use local IIS web server

A sample MVC application in Visual Studio 2010 configured to use local IIS web server

1. Enable profiling for w3wp.exe.

a) Find the application pool for the app.

Check IIS Manager, Sites – Default Web Site – MvcApplication1, Basic Settings. In my case the pool is DefaultAppPool:

Application pool in IIS manager

Application pool in IIS manager

b) Enable user profile loading for the pool.

IIS Manager, Application Pools, DefaultAppPool, Advanced Settings, Process Model – Load User Profile, set to True:

Application pools in IIS manager

Application pools in IIS manager


Advanced application pool settings

Advanced application pool settings

c) Find SID of the pool account.

From the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList key find ProfileImagePath with DefaultAppPool. In my case the SID is S-1-5-82-3006700770-424185619-1745488364-794895919-4004696415:

DefaultAppPool SID in registry

DefaultAppPool SID in registry

d) Set environment variables to invoke Runtime Flow profiler.

Using the found SID, add two string values to HKEY_USERS\S-1-5-82-3006700770-424185619-1745488364-794895919-4004696415\Environment:

Cor_Enable_Profiling=1
COR_PROFILER={C967CF3F-79BF-49a5-A10F-D5B269DB9E54}

Environment settings for DefaultAppPool

Environment settings for DefaultAppPool


Note that if you use IntelliTrace it can overwrite these registry values.

2. Close all running w3wp.exe processes.

In IIS Manager restart server.

3. Run monitoring.

In Runtime Flow – Customized Run, uncheck Stop monitoring when the command completes. Set Command to “C:\Program Files\Internet Explorer\iexplore.exe”. Set Command arguments to “http://localhost/MvcApplication1”. Optionally set Options – Monitoring Filter to “Module == MvcApplication1.dll”:

Customized run of Internet Explorer

Customized run of Internet Explorer


After you click Run, you will see how your application runs:
Runtime Flow monitoring results

Runtime Flow monitoring results

December 14, 2011

Runtime Flow v1.3.2 released

Filed under: Uncategorized — Sergey Vlasov @ 4:43 pm

Runtime Flow v1.3.2 released: fixed compound exceptions handling.

Download links: Visual Studio edition, Portable edition.

September 11, 2011

Runtime Flow v1.3.1 released

Filed under: Uncategorized — Sergey Vlasov @ 12:06 pm

Runtime Flow v1.3.1 released – added a .NET 4.0 portable edition executable with deeper call stack support, enabled Options during monitoring.

Download links: Visual Studio edition, Portable edition.

Older Posts »

Create a free website or blog at WordPress.com.