While we are at it Peter  -

I am successfully using the application to profile asp.net applications. Not
only with the SYSTEM account, but also with user accounts that have
administrator (and perhaps "act as part of the operating system") rights.

What I would like to know is:

1. Any comments on its use with multiple asp.net apps on the same box? i.e.
both a web app and a web service running on the same machine. I get the
feeling it works by first come first server principle.

2. I can't get the histogram by age to work. But then, that didn't work for
the version on gotdotnet either, so it might be a problem on my end.
I am running WinXP with both fw 1.0 and 1.1 installed (it seems to be using
the 1.0 fw - but that might have to do with my asp.net app). I had this
issue with both asp.net and winforms apps.

The error is reported as follows, just after the window opens (but with big
crossed out windows inside:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
  at System.Number.ParseDouble(String s, NumberStyles style,
NumberFormatInfo info)
  at System.Double.Parse(String s, NumberStyles style, IFormatProvider
provider)
  at System.Double.Parse(String s)
  at CLRProfiler.AgeHistogram.GetTimeScale(Double suggestedScale)
  at CLRProfiler.AgeHistogram.Init(Graphics g)
  at CLRProfiler.AgeHistogram.typeLegendPanel_Paint(Object sender,
PaintEventArgs e)
  at System.Windows.Forms.Control.OnPaint(PaintEventArgs e)
  at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e,
Int16 layer, Boolean disposeEventArgs)
  at System.Windows.Forms.Control.WmPaint(Message& m)
  at System.Windows.Forms.Control.WndProc(Message& m)
  at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
  at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
  at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
  at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
   Assembly Version: 1.0.3300.0
   Win32 Version: 1.0.3705.288
   CodeBase:
file:///c:/windows/microsoft.net/framework/v1.0.3705/mscorlib.dll
----------------------------------------
CLRProfiler
   Assembly Version: 1.0.1395.16737
   Win32 Version: 1.0.1395.16737
   CodeBase: file:///c:/CLR%20Profiler/Binaries/CLRProfiler.exe
----------------------------------------
System.Windows.Forms
   Assembly Version: 1.0.3300.0
   Win32 Version: 1.0.3705.288
   CodeBase:
file:///c:/windows/assembly/gac/system.windows.forms/1.0.3300.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
   Assembly Version: 1.0.3300.0
   Win32 Version: 1.0.3705.288
   CodeBase:
file:///c:/windows/assembly/gac/system/1.0.3300.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
   Assembly Version: 1.0.3300.0
   Win32 Version: 1.0.3705.288
   CodeBase:
file:///c:/windows/assembly/gac/system.drawing/1.0.3300.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Xml
   Assembly Version: 1.0.3300.0
   Win32 Version: 1.0.3705.288
   CodeBase:
file:///c:/windows/assembly/gac/system.xml/1.0.3300.0__b77a5c561934e089/system.xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
   <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.

I feel silly, but how do you make the ASPNET process run
as SYSTEM?