troubleshooting arcgis web api’s (javascript, flex, silverlight) from a support p erspective

Esri International User Conference | San Diego, CA

July 14, 2011

Troubleshooting ArcGIS Web API’s (JavaScript, Flex, Silverlight) from a Support Perspective

Doug Carroll and Heather Gonzago

Overview

• Debugging tools and resources

• Application setups and patterns

• Common troubleshooting samples

• How to troubleshoot intermittent problems

Web Browser Debugging Tools

• Tools that allow client –side debugging of web page components, e.g.- HTML

- CSS

- JavaScript

- HTTP Traffic

• Provides QA, saves time, and aids in troubleshooting errors

Common Web Browser Debugging Tools

• Most commonly used in Support- Browser-based

- Fiddler (Microsoft)

- Firebug (Mozilla)

- IE Developer Tools

- Chrome’s integrated web kit tools

- Charles*

• Development Environments- Microsoft Visual Studio

- Eclipse / Flash Builder

- Aptana

Web Browser Debugging Tool Links

Troubleshooting Demos

JavaScript, Flex and Silverlight Demos

• JavaScript API Debugging (Firebug | Aptana) – Console logging, HTTP Traffic monitoring, code stepping and error trapping

• Silverlight API Debugging (Fiddler | Visual Studio) – HTTP Traffic monitoring, code stepping and error trapping

• Flex API Debugging (Charles | Flash Builder) – Binary HTTP Traffic monitoring, code stepping and error trapping

What about Debugging Viewers?

• Silverlight Viewer Add-in Debugging (Fiddler | Visual Studio) – Attaching to Process, HTTP Traffic monitoring and code stepping

• Flex Viewer Widgets – These are debugged using the same technique as standard Flex API applications

Questions?