Page History

...

• DLL list. A list of DLLs to be instrumented and specific configuration rules for each DLL. If the underlying process of the instance should be instrumented, it must be mentioned explicitly.
• Common instrumentation rules (“instrument”"instrument") for the whole DLL list.
• Common exclude rules (“ignore”"ignore"). Following is an example of the file structure:

...

In the following example, all DLLs with the prefix “Pet” "Pet" are instrumented and tracked, regardless of their path. Likewise, for the classes with the prefix “Pet”, "Pet" all methods are instrumented and tracked.

...

1. After the Microsoft .NET instance is installed, configure the DLLs, classes, and methods to be instrumented in the instrumentation.xml file.
2. Open a command prompt window and run the following command:
        cd <i3_root>
        products\dotnet\bin\psdn_instr_validate.exe [-k instance-name]
        -f directory-name | -dll name [-gac]
   where:
   instance-name is the Microsoft .NET instance name, such as AspNetIIS5. If this parameter is omitted, the Instrumentation Driver works for all the Microsoft .NET instances that are installed on the monitored server. 
   directory-name is the name of the DLL directory of the Microsoft .NET instance to be instrumented. This is the location where you deployed your Microsoft .NET code. For example, a DLL for an ASP.NET application may be stored in:
         C:\Inetpub\wwwroot\MyWebApp\bin
   name is the name of a single DLL (without the path). If this DLL is located in the GAC, add -gac when running the command.

...