{"id":8363,"date":"2015-03-09T17:00:00","date_gmt":"2015-03-09T17:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2015\/03\/09\/editing-the-intellitrace-collection-plan\/"},"modified":"2022-07-28T00:44:35","modified_gmt":"2022-07-28T08:44:35","slug":"editing-the-intellitrace-collection-plan","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/editing-the-intellitrace-collection-plan\/","title":{"rendered":"Editing the IntelliTrace collection plan"},"content":{"rendered":"

As you probably already know, Visual Studio offers an enhanced debugging experience through the use of IntelliTrace<\/a>. Your application\u2019s execution is recorded by IntelliTrace and you can navigate through time, both backwards and forwards, and examine your code as you normally would during a debugging session by interacting with the Call Stack and Locals windows.<\/p>\n

The collection plan is the compilation of all settings that tell IntelliTrace what data to collect while the application is running:<\/p>\n

    \n
  1. What interesting events to collect<\/li>\n
  2. Whether to collect method calls and parameters<\/li>\n
  3. Whether to whitelist or blacklist certain assemblies<\/li>\n<\/ol>\n

    When you are using IntelliTrace within Visual Studio, you change these settings through Tools > Options > IntelliTrace<\/strong>:<\/p>\n

    \"image\"<\/p>\n

    The IntelliTrace standalone collector<\/a> does not have a graphical UI, it uses PowerShell commands<\/a> instead. One of the arguments to the command that starts collection is the path to an .xml file that represents the collection plan. The download for the collector contains two collection plans out of the box:<\/p>\n