{"id":183,"date":"2014-12-16T17:40:00","date_gmt":"2014-12-16T17:40:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2014\/12\/16\/custom-tracesource-and-debugging-using-intellitrace\/"},"modified":"2022-05-26T01:25:19","modified_gmt":"2022-05-26T09:25:19","slug":"custom-tracesource-and-debugging-using-intellitrace","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/custom-tracesource-and-debugging-using-intellitrace\/","title":{"rendered":"Custom TraceSource and debugging using IntelliTrace"},"content":{"rendered":"

IntelliTrace<\/a> in Visual Studio Enterprise comes with support for tracing out of the box. All you have to do is make sure the appropriate IntelliTrace events are enabled in VS settings and IntelliTrace will capture trace statements as events.<\/p>\n

\"\"<\/p>\n

When you are not using the default Debug.Trace methods and are instead using a custom TraceSource<\/a>, you don\u2019t want to rewrite your tracing code just to get the trace data captured by IntelliTrace. This blog post will explain how to add support for events from a custom TraceSource<\/a> in addition to the events listed in VS settings (see screenshot above).<\/p>\n

If you’d like, you can download the source code and follow along as well as the .itrace file<\/a> that was generated.<\/p>\n

Overview<\/h2>\n
    \n
  1. Create a custom TraceListener specifically for IntelliTrace<\/li>\n
  2. Enable the custom TraceListener for your application<\/li>\n
  3. Update the collection plan XML file to tell IntelliTrace about the custom TraceListener<\/li>\n
  4. IntelliTrace will now pick up all messages that are sent to the custom TraceListener<\/li>\n<\/ol>\n

    Step 1 \u2013 Create a custom trace listener specifically for IntelliTrace<\/h2>\n

    Create a class that extends TraceListener (you will need a reference to System.Diagnostics). In this example we are using the namepace \u201cCustomTracing\u201d, we will need to know this later on. You can use a difference namespace for your TraceListener, but make sure you use that same namespace whenever we are using \u201cCustomTracing\u201d throughout this example.<\/p>\n

    \n Code: <\/p>\n
    using<\/span> System;\nusing<\/span> System.Diagnostics;\n\nnamespace<\/span> CustomTracing\n{\n    class<\/span> TraceListenerForIntelliTrace<\/span> : TraceListener<\/span>\n    {\n        \/\/\/<\/span><summary><\/span>\n        \/\/\/<\/span> A class scope variable that holds the contents of the current<\/span>\n        \/\/\/<\/span> trace message being sent to this custom TraceListener.<\/span>\n        \/\/\/<\/span> We can expect multiple .Write(string) calls and one final<\/span>\n        \/\/\/<\/span> .WriteLine(string) call that will signify the end of the message.<\/span>\n        \/\/\/<\/span><\/summary><\/span>\n        private<\/span> string<\/span> message = String<\/span>.Empty<\/span>;\n\n        public<\/span> override<\/span> void<\/span> WriteLine(string<\/span> message)\n        {\n            \/\/ Since we are told to WriteLine now, it means<\/span>\n            \/\/ this is the last part of the message<\/span>\n            this<\/span>.message += message;\n            this<\/span>.WriteMessage(this<\/span>.message);\n\n            \/\/ Since we just wrote the last part of the messsage<\/span>\n            \/\/ reset the class scope variable to an empty string<\/span>\n            \/\/ to prepare for the next message<\/span>\n            this<\/span>.message = String<\/span>.Empty<\/span>;\n        }\n\n        public<\/span> override<\/span> void<\/span> Write(string<\/span> message)\n        {\n            \/\/ Since we are told to just Write and not WriteLine<\/span>\n            \/\/ it means there is more to come for this message, so<\/span>\n            \/\/ use a class scope variable to build up the message<\/span>\n            this<\/span>.message += message;\n        }\n\n        public<\/span> void<\/span> WriteMessage(string<\/span> message)\n        {\n            \/\/ Do nothing here, we just need the method to exist<\/span>\n            \/\/ so that IntelliTrace can hook into it and extract<\/span>\n            \/\/ the parameter \"message\"<\/span>\n        }\n    }\n}\n\n\n<\/pre>\n<\/div>\n
    Step 2 – Enable the custom TraceListener for your application<\/h2>\n
    Make the following changes to app\u2019s config. The highlighted<\/span> parts will need to be updated with the appropriate namespace and class name that you choose for your custom TraceListener.<\/p>\n
    <\/p>\n
    <<\/span>system.diagnostics<\/span>><\/span>\n    <<\/span>sources<\/span>><\/span>\n      <<\/span>source<\/span> name<\/span>=\"TraceTest\"<\/span> switchName<\/span>=\"SourceSwitch\"<\/span>\n        switchType<\/span>=\"System.Diagnostics.SourceSwitch\"<\/span> ><\/span>\n        <<\/span>listeners<\/span>><\/span>\n          <<\/span>add<\/span> name<\/span>=\"TraceListenerForIntelliTrace<\/span>\"<\/span> type<\/span>=\"CustomTracing.TraceListenerForIntelliTrace, CustomTracing<\/span>\"<\/span>\/><\/span>\n          <<\/span>remove<\/span> name<\/span> =\"Default\"<\/span> \/><\/span>\n        <\/<\/span>listeners<\/span>><\/span>\n      <\/<\/span>source<\/span>><\/span>\n    <\/<\/span>sources<\/span>><\/span>\n    <<\/span>switches<\/span>><\/span>\n      <!-- You can set the level at which tracing is to occur --><\/span>\n      <<\/span>add<\/span> name<\/span>=\"SourceSwitch\"<\/span> value<\/span>=\"Information\"<\/span> \/><\/span>\n      <!-- You can turn tracing off --><\/span>\n      <!--add name=\"SourceSwitch\" value=\"Off\" --><\/span>\n    <\/<\/span>switches<\/span>><\/span>\n<\/<\/span>system.diagnostics<\/span>><\/span>\n<\/pre>\n
    Step 3 – Update the collection plan XML file to tell IntelliTrace about the custom TraceListener<\/h2>\n
    Add the following XML fragment just before the <\/ModuleSpecifications>\u00a0closing tag. The highlighted part<\/span> will need to be updated with the name of the assembly that contains your custom TraceListener.<\/p>\n
    <\/p>\n
    <<\/span>ModuleSpecification<\/span> Id<\/span>=\"custom\"<\/span>><\/span>CustomTracing.exe<\/span><\/<\/span>ModuleSpecification<\/span>><\/span><\/pre>\n
    Add the following XML fragment just before the <\/DiagnosticEventSpecifications> closing tag. The highlighted parts<\/span> will need to be updated with the appropriate namespace and class name that you choose for your custom TraceListener.<\/p>\n
    <\/p>\n
    <<\/span>DiagnosticEventSpecification<\/span> enabled<\/span>=\"true\"<\/span>><\/span>\n        <<\/span>CategoryId<\/span>><\/span>tracing<\/<\/span>CategoryId<\/span>><\/span>\n        <<\/span>SettingsName<\/span> _locID<\/span>=\"settingsName.Custom\"<\/span>><\/span>Custom TraceSource<\/<\/span>SettingsName<\/span>><\/span>\n        <<\/span>SettingsDescription<\/span> _locID<\/span>=\"settingsDescription.Custom\"<\/span>><\/span>Custom TraceSource<\/<\/span>SettingsDescription<\/span>><\/span>\n        <<\/span>Bindings<\/span>><\/span>\n          <<\/span>Binding<\/span>><\/span>\n            <<\/span>ModuleSpecificationId<\/span>><\/span>custom<\/<\/span>ModuleSpecificationId<\/span>><\/span>\n            <<\/span>TypeName<\/span>><\/span>CustomTracing.TraceListenerForIntelliTrace<\/span><\/<\/span>TypeName<\/span>><\/span>\n            <<\/span>MethodName<\/span>><\/span>WriteMessage<\/<\/span>MethodName<\/span>><\/span>\n            <<\/span>MethodId<\/span>><\/span>CustomTracing.TraceListenerForIntelliTrace.WriteMessage(System.String):System.Void<\/span><\/<\/span>MethodId<\/span>><\/span>\n            <<\/span>ShortDescription<\/span> _locID<\/span>=\"shortDescription.Custom\"<\/span>><\/span>\"{0}\"<\/<\/span>ShortDescription<\/span>><\/span>\n            <<\/span>LongDescription<\/span> _locID<\/span>=\"longDescription.Custom\"<\/span>><\/span>\"{0}\"<\/<\/span>LongDescription<\/span>><\/span>\n            <<\/span>DataQueries<\/span>><\/span>\n              <<\/span>DataQuery<\/span> index<\/span>=\"1\"<\/span> maxSize<\/span>=\"4096\"<\/span> type<\/span>=\"String\"<\/span> name<\/span>=\"message\"<\/span> _locID<\/span>=\"dataquery.Custom.text\"<\/span> _locAttrData<\/span>=\"name\"<\/span> query<\/span>=\"\"<\/span>><\/<\/span>DataQuery<\/span>><\/span>\n            <\/<\/span>DataQueries<\/span>><\/span>\n         <\/<\/span>Binding<\/span>><\/span>\n        <\/<\/span>Bindings<\/span>><\/span>\n      <\/<\/span>DiagnosticEventSpecification<\/span>><\/span>\n<\/pre>\n
    Where to make this change when using F5\/Attach<\/strong><\/p>\n
    If you are using F5\/Attach to debug the application, then you need to change the \u201ccollectionplan.xml\u201d file found here:
    \nC:Program Files (x86)Microsoft Visual Studio [Version of your VS]Common7IDECommonExtensionsMicrosoftIntelliTrace[Version of your VS]en<\/p>\n
    For example, for VS 2013:
    \nC:Program Files (x86)Microsoft Visual Studio 12.0Common7IDECommonExtensionsMicrosoftIntelliTrace12.0.0en<\/p>\n
    Where to make this change when using the IntelliTraceStandalone Collector<\/strong><\/p>\n
    If you are using the IntelliTrace Standalone Collector<\/a> then you need to change the collection plan .xml file that you pass in as an argument using PowerShell. More information on how to use the standalone collector<\/a>.<\/p>\n
    Where to make this change when using Microsoft Monitoring Agent (MMA)<\/strong><\/p>\n
    If you are using MMA<\/a> then you need to change the collection plan .xml file that you pass in as an argument using PowerShell and the Start-WebApplicationMonitoring command. If you are not used to providing a custom collection plan, you can find the default collection plans here:
    \nC:Program FilesMicrosoft Monitoring AgentAgentIntelliTraceCollector<\/p>\n
    Where to make this change when using Azure<\/strong><\/p>\n
    When you publish your project to Azure, you get the choice to enable IntelliTrace and change its settings<\/p>\n
    \"\"<\/p>\n
    Clicking \u201cSettings\u2026\u201d shows this dialog which looks just like the Visual Studio settings for IntelliTrace, but it\u2019s not quite the same:<\/p>\n
    \"\"<\/p>\n
    As a result of enabling IntelliTrace and changing the settings a new collectionplan.xml file will appear here:
    \n%appdata%MicrosoftVisualStudio12.0Cloud Tools<\/p>\n
    This is the actual XML file that gets uploaded to Azure. So it\u2019s this XML file that you need to add the XML fragment to for the custom TraceListener.<\/p>\n
    Step 4 – IntelliTrace will now pick up all messages that are sent to the custom TraceListener<\/h2>\n
    My demo console app below is trying to write 3 different trace messages<\/p>\n
    \n  Code: <\/p>\n
    using<\/span> System;\nusing<\/span> System.Diagnostics;\n\nnamespace<\/span> CustomTracing\n{\n    class<\/span> Program<\/span>\n    {\n        static<\/span> TraceSource<\/span> ts = new<\/span> TraceSource<\/span>(\"TraceTest\"<\/span>);\n\n        static<\/span> void<\/span> Main(string<\/span>[] args)\n        {\n            ts.TraceInformation(\"Trace using TraceSource.TraceInformation\"<\/span>);\n            ts.TraceEvent(TraceEventType<\/span>.Information, 1, \"Trace using TraceSource.TraceEvent\"<\/span>);\n            ts.TraceEvent(TraceEventType<\/span>.Error<\/span>, 2, \"Trace using TraceSource.TraceEvent\"<\/span>);\n\n            Console<\/span>.WriteLine(\"Hit enter to exit...\"<\/span>);\n            Console<\/span>.ReadLine();\n        }\n    }\n}\n\n\n<\/pre>\n<\/div>\n
    so I expect IntellITrace to pick up 3 separate trace events<\/p>\n
    \"\"<\/p>\n
    Bonus Step 5 \u2013 Customizing your trace messages<\/h2>\n
    You have two ways to customize the way your trace messages are captured by IntelliTrace:<\/p>\n
      \n
    1. Manipulate the string within your custom TraceListener class before calling method WriteMessage(string message) is called.<\/li>\n
    2. Change the .xml collection plan file, and more specifically the elements ShortDescription (what IntelliTrace shows in VS while the event is collapsed) and LongDescription (what IntelliTrace shows in VS while the event is selected and expanded<\/li>\n<\/ol>\n
      \n  This just prints out the trace message as a whole:\n<\/div>\n
      <\/p>\n
      <<\/span>ShortDescription<\/span> _locID<\/span>=\"shortDescription.Custom\"<\/span>><\/span>\"{0}\"<\/<\/span>ShortDescription<\/span>><\/span>\n<<\/span>LongDescription<\/span> _locID<\/span>=\"longDescription.Custom\"<\/span>><\/span>\"{0}\"<\/<\/span>LongDescription<\/span>><\/span><\/pre>\n
      \n  This changes the long version of the trace message:\n<\/div>\n
      <\/p>\n
      <<\/span>ShortDescription<\/span> _locID<\/span>=\"shortDescription.Custom\"<\/span>><\/span>\"{0}\"<\/<\/span>ShortDescription<\/span>><\/span>\n<<\/span>LongDescription<\/span> _locID<\/span>=\"longDescription.Custom\"<\/span>><\/span>Trace captured by custom TraceListener: \"{0}\"<\/<\/span>LongDescription<\/span>><\/span><\/pre>\n
      \n  We are always looking for feedback and comments for our features. Please send us a tweet<\/a> or visit the MSDN Diagnostics forums<\/a>.\n<\/div>\n
      CustomTracing (source code).zip<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
      IntelliTrace in Visual Studio Enterprise comes with support for tracing out of the box. All you have to do is make sure the appropriate IntelliTrace events are enabled in VS settings and IntelliTrace will capture trace statements as events. When you are not using the default Debug.Trace methods and are instead using a custom TraceSource, […]<\/p>\n","protected":false},"author":127,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[226,1,225],"tags":[],"class_list":["post-183","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ci","category-devops","category-git"],"acf":[],"blog_post_summary":"
      IntelliTrace in Visual Studio Enterprise comes with support for tracing out of the box. All you have to do is make sure the appropriate IntelliTrace events are enabled in VS settings and IntelliTrace will capture trace statements as events. When you are not using the default Debug.Trace methods and are instead using a custom TraceSource, […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/183","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/127"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=183"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/183\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/45953"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=183"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=183"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=183"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}