Sign in to queue
Defrag Tools

Defrag Tools: #37 - JavaScript - Part 1

Play Defrag Tools: #37 - JavaScript - Part 1

Download this episode

Download Video

Description

In this episode of Defrag Tools, Andrew Richards, Amanda Silver and Larry Larsen start walking you through the debugging of JavaScript Windows Store applications with Visual Studio. Amanda is a Principal developer for the JavaScript engine used in Internet Explorer, Windows Store applications and Visual Studio.

Timeline:
[00:54] - Debugging a JavaScript Windows Store application
[02:30] - Catching Crashes (unhandled exceptions)
[04:25] - WinJS.Utilities.startLog
[05:22] - app.onerror
[09:30] - Stacks
[11:47] - e.detail.error.stack
[14:23] - use strict
[20:25] - www.jslint.com integrated in VS
[22:13] - "Pin" bug
[24:58] - tile vs. title - Lint cannot detect this
[26:50] - Next time... more JavaScript debugging!

Tags:

Debugging, JavaScript, Troubleshooting

Embed

Format

Available formats for this video:

Actual format may change based on video formats available and browser capability.

    More episodes in this series

    Related episodes

    The Discussion

    • User profile image
      FFE

      Thank you.

      good to know of "use strict"; a feature that will certainly help. It'd be nice to be able to turn off on a per file basis. For example, in in the beginning of legacy files one can put "use strict not"; or something similar.

       

    • User profile image
      Edward

      Can you apply "use strict" to the entire Java engine? (like you would server side with C# with web.config)
      It seems to be a great way to do final runtime checks on your farm of test machines - that, as you say, might concat' in a different order.

    • User profile image
      meutinee

      My computer graphics,. arent working correctly. dont want to bother anyone...neither is wmp pics nor will any devices be recognized. was working two weeks ago. all but wmp. i have java and flashplayer intalled and active x disabled. what should i do???!

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.