debugging apps & analysing usage

www.xpand-it.com Proprietary & Confidential

Debugging Apps and Analysing Usage

with Visual Studio 2013

Visual Studio 2013 Airlift

05-12-2013

[email protected]

2003 - 2013 © Copyright Xpand IT www.xpand-it.com

• Jorge Borralho

• 8+ years in application development

– mainly with Microsoft products – C#, asp.net, mvc, sharepoint, sql server

who am i


abstract

x64 bits edit & continue

• Debug tools

Code map

Asynchronous Debugging

Just my code (javascript)

Return value inspection

Intelitrace debugging

Microsoft Monitoring Agent

• Profiling tools

Dump file analysis

Energy consumption


x64 edit & continue

• Must target 4.5.1

• Using 3rd party hosts must use IIS Express


Return value inspection

• Inspect functions/nested functions return values relevant to current debugging session

Demo


Asynchronous debugging

• Simplified infraestructure code in call stack

• Visualize tasks

VS 2012

VS 2013


Just my code – JS & C++

• Step through 3rd party code right to your code;

• Ignore Exceptions managed by 3rd party code.

Demo


Code map

• Enhanced Call Stack

Demo


MMA & Intelitrace Debugging

• Diagnose problems in deployment with Visual Studio and Microsoft Monitoring Agent

• Enabling MMA: – Configure witch modules to monitor

– Start monitoring (defining trace level)

– Capture Intelitrace snapshot

• Impacts app performance – Enabled to whole application pool

– Captures (almost) every object value in method-calls from defined modules

<ModuleList isExclusionList="false"> <Name>PublicKeyToken:B77A5C561934E089</Name> <Name>PublicKeyToken:B03F5F7F11D50A3A</Name> <Name>PublicKeyToken:31BF3856AD364E35</Name> <Name>PublicKeyToken:89845DCD8080CC91</Name> <Name>PublicKeyToken:71E9BCE111E9429C</Name> </ModuleList>

PS C:\>Start-WebApplicationMonitoring "IIS:\Test.Web" Monitor

"C:\IntelliTraceLogs”



• Debugging from Intelitrace Log

– Matching source files and symbols (.pdb)

– Visual Studio 2013 ultimate

– .iTrace file



• Review Performance Violation (1/3)

Review recorded events and choose to “dig deeper”




See multiple calls to this event, review slowest ones and debug them




Review call stack, recorded values, step through and access Intelitrace



• Exception Data

Get all exceptions recorded – and debug them



• Analysing Sharepoint unhandled exception (1/3)

Get the Correlation Id




Go to Analysis in the iTrace file and search by correlation Id




Get full info in the exception, step into the intelitrace in that moment


Dump file analysis

• When a long running app starts behaving sluggishly or crashes with OutOfMemoryException, or even the whole server/system slows down

– Probably bad memory usage:

• Memory leaks

• Unnecessary allocation

• Inefficient memory use

• Better analyze the memory dump

– using task manager, procdump (sysinternals) or even VS 2013 (capturing a breakpoint)


Dump file analysis

• Analyse them directly in visual studio

Demo


Energy Consumption (1/3)

• The Visual Studio Energy Consumption profiler helps you analyze the power and energy consumption of Windows Store apps on low-power tablet devices that run all or part of the time on their own batteries. On a battery-powered device, an app that uses too much energy can cause so much customer dissatisfaction that, eventually, customers might even uninstall it. Optimizing energy use can increase your app’s adoption and use by customers.



• What’s measured?

• Mark profiling data



• Configure device and collect data

• Profile data


Q & A

[email protected]

mailto:[email protected]



debugging apps & analysing usage

Technology

mma intelitrace debugging

debugging apps

access intelitrace

energy use

party code

review performance violation

pdb visual studio

memory dump