Day 2 Keynote Presentation
Description
Debugging and diagnosing your Web apps just gets better; a whirlwind tour of enhancements in your in-browser developer tools, F12.
For more information, check out these courses on Microsoft Virtual Academy:
Day:
1Level:
300 - ExperiencedSession Type:
BreakoutCode:
3-638Room:
Room 3022Share
Download
Download this episode
- MP3 (50.5 MB)
- Mid Quality MP4 (157.7 MB)
- High Quality MP4 (0.0 B)
- Low Quality MP4 (0.0 B)
Download captions
For more information, check out these courses on Microsoft Virtual Academy:
Event Homepage
Build 2015More episodes in this series
All Things Azure
Related episodes
Tips for Working with CSS in the Edge Dev Tools
Debugging Events in Edge
TracePoints, a Better Way to console.log
Tips for Using the F12 Edge Dev Tools
Tips for Using the F12 Edge Dev Tools
F12 Edge Developer Tools
What’s new in the F12 Developer Tools
Internet Explorer 11’s Developer Tools, F12, Just Got Nicer (Again)
Diagnosing Issues with Windows Phone JavaScript Apps Using Visual Studio
Website and Web App Platform Leadership Team: A Panel Discussion
The Discussion
-
John Great Speaker. Excellent contents
-
beautifulcoder I've spent hours looking for elusive click events in my DOM. This debugger will be life changing!
-
Joel They should have kept the Spartan name for the browser.
-
minu Wonderful session..I've one question..
I've a Win32 app and I would want my application to use spartan for launching links if spartan is set as default browser. Through registry I will currently find out the presence of other browsers (like IE, chrome, etc) and will use reg to identify their install location and launch links. How would I achieve the same if spartan is set as default browser?
which reg key should I look out for?
Thanks!
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.