Configuration for .NET Monitoring
Attach Profiler to Running .NET Application
Starting with .NET4, it is possible to dynamically attach the profiler to a running CLR. To do so, run the following command with specific process ID:

ProfilerConsole.exe for .NET - Germain UX
Launch .Net Application with Profiler Attached
The profiler console can be used to list all currently running .NET CLRs. Please note, that the 32 and 64 bit versions of the console will only show .NET CLRs of the corresponding architecture (i.e., 64 bit console will only show 64 bit CLRs).

ProfilerConsole.exe for .NET (2) - Germain UX
For each CLR, the console will display the process ID, CLR version, and application path. For a list of .NET runtime versions, see https://msdn.microsoft.com/en-us/library/w4atty68(v=vs.110).aspx#version .
To start profiling a new .NET executable, run the following command:

ProfilerConsole.exe for .NET (3) - Germain UX
Profiling to a http://ASP.NET Application
The following instructions are specific to monitoring Internet Information Services (IIS), but should be applicable to monitoring other Windows services as well.
Create new environment variables to enable profiling:
w3wp.exe - Germain UX
Create an environment variable for the profiler class ID ({D768E37F-294B-43D3-9178-250C40F6F8C1}):
Add COR_PROFILER variable - Germain UX
Create registry key to specify the executable to monitor under HKEY_LOCAL_MACHINE\SOFTWARE\Germain Software\Germain Profiler
Add COR_ENABLE_PROFILING variable - Germain UX
Restart the server to apply the environment variables. The profiler will automatically attach the next time the IIS service is started.
Component: Code Profiler
Feature Availability: 8.6.0 or later