IntelliTrace for WCF Services

1 post · Dec 2012 – Oct 2013

What this trail covers

IntelliTrace is enhanced with an Analysis section on the Summary Page to help pinpoint bugs faster by analyzing logs for specific patterns and events indicating problems. In Update 1, this section focuses on highlighting unhandled exceptions in SharePoint applications, aggregating occurrences and providing direct links to the relevant code for debugging. VS2012 Update 2 extends these capabilities to SharePoint applications by collecting ULS log entries as IntelliTrace events, associating them with Correlation IDs, and enabling filtering by Correlation ID in the IntelliTrace window for debugging SharePoint applications.

All Microsoft trails

Oct 2013IntelliTrace and WCF Services called by SilverlightThis post addresses a limitation where IntelliTrace was not supported for Silverlight applications. It explains that IntelliTrace *is* supported for WCF services hosted in IIS/IIS Express, even when called by Silverlight. The key technical contribution is the instruction on how to switch the debug process in Visual Studio Ultimate from the Internet Explorer (hosting Silverlight) process to the IIS Express process to view IntelliTrace data for the WCF service.
Apr 2013System Center and IntelliTraceThis post details the integration of System Center 2012 SP1 Application Failure events with Visual Studio Ultimate 2012 Update 2 IntelliTrace files. It explains how to assign operational issues from System Center to engineering teams in Team Foundation Server, automatically linking IntelliTrace files to work items. It also covers enabling full IntelliTrace data collection for challenging problems and storing IntelliTrace files locally if TFS integration is not used. A virtual machine and hands-on-lab are provided for exploration.
Apr 2013ALM Rangers ship guidance for DevOps bug resolution using IntelliTraceThis post announces the release of new guidance focused on IntelliTrace for DevOps bug resolution. It includes epics and artifacts such as cheatsheets, hands-on labs, and posters covering build master, developer, and operations views of IntelliTrace in DevOps scenarios. Specific labs cover symbol configuration, build, client-side resolution without symbols, and collection for WPF rich client applications.
Feb 2013Debugging Unhandled Exceptions in a SharePoint App with Visual Studio using IntelliTraceIntroduced an 'Analysis' section to the IntelliTrace Summary Page, specifically focusing on highlighting unhandled exceptions in SharePoint applications. This section aggregates occurrences of unhandled exceptions and provides a direct 'Debug Exception' link to navigate to the code where the exception was thrown. The post also details a walkthrough of collecting IntelliTrace logs for a SharePoint application, stopping collection, opening the log, and using the Analysis section to debug a System.Net.WebException, demonstrating how to filter events by Correlation ID and apply code fixes.
Jan 2013VS2012 Update 2 Brings Symbol Improvements to Profiler and IntelliTraceVisual Studio 2012 Update 2 applies the symbol loading logic previously updated for the debugger in Update 1 to IntelliTrace scenarios (live debugging and .iTrace file analysis) and performance analysis of Windows Store apps and CPU sampling. This improves both performance and usability by using the same symbol loading mechanism. Manual symbol loading through the Modules window is also improved to be cancellable and benefit from caching.
Advertisement
Dec 2012Debugging SharePoint Apps with IntelliTrace in Visual StudioThis post details the integration of IntelliTrace with Visual Studio 2012 Ultimate Update 2 for debugging SharePoint 2013 and 2010 applications. It explains how SharePoint's Unified Logging System (ULS) and Correlation IDs work, and how IntelliTrace now collects ULS log entries as IntelliTrace events, including Correlation IDs. A walkthrough demonstrates collecting an IntelliTrace log from a malfunctioning SharePoint application, using the Correlation ID to filter events, identifying a System.Net.WebException as the root cause, and directly navigating to the problematic code for debugging and resolution.