{"id":5104,"date":"2007-03-08T20:03:00","date_gmt":"2007-03-08T20:03:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/webdev\/2007\/03\/08\/jscript-debugging-in-visual-web-developer-orcas\/"},"modified":"2007-03-08T20:03:00","modified_gmt":"2007-03-08T20:03:00","slug":"jscript-debugging-in-visual-web-developer-orcas","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/jscript-debugging-in-visual-web-developer-orcas\/","title":{"rendered":"JScript Debugging in Visual Web Developer Orcas"},"content":{"rendered":"<p><P><SPAN>Jeff King made a recent post to show off the new <A class=\"\" href=\"http:\/\/blogs.msdn.com\/webdevtools\/archive\/2007\/03\/02\/jscript-intellisense-in-orcas.aspx\">JScript IntelliSense<\/A>&nbsp;feature <SPAN>in the <A class=\"\" href=\"http:\/\/www.microsoft.com\/downloads\/details.aspx?FamilyID=b533619a-0008-4dd6-9ed1-47d482683c78&amp;DisplayLang=en\">March CTP<\/A> of Visual Studio. Now I am going to show off the improved JScript Debugging&nbsp;experience in the March CTP.<\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN>The first thing you will notice is that when you try to debug an IE page, VS will give you a nice little dialog reminding you to turn on script debugging in IE:<\/SPAN><\/SPAN><\/P>\n<P><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/JScript%20Warning.jpg\"><\/P>\n<P>&nbsp;<\/P>\n<P><SPAN><SPAN>Here is the Advance tab in IE:<\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/Internet%20Options.jpg\"><\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><\/SPAN><\/SPAN>&nbsp;<\/P>\n<P><SPAN><SPAN>After you&#8217;ve turned on script debugging in IE, you can set a breakpoint in your ASPX document right away!<\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/JScript%20Mapped%20BP.jpg\"><\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN>You might notice a little diamond inside the breakpoint glyph and wonder what that means. The little diamond indicates this is a mapped breakpoint. This breakpoint will get mapped automatically to the run-time document when you debug the page (F5).<\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><\/SPAN><\/SPAN>&nbsp;<\/P>\n<P><SPAN><SPAN>Debug the page&nbsp;(F5) and&nbsp;VS will pause at the breakpoint:<\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/JScript%20Hit%20BP.jpg\"><\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><\/SPAN><\/SPAN>&nbsp;<\/P>\n<P><SPAN><SPAN>If you look closely, the execution actually paused in the run-time document instead of the design-time document:<\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/JScript%20Run-Time%20Document.jpg\"><\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN>You can set breakpoints in the&nbsp;run-time document and&nbsp;they will&nbsp;get saved back&nbsp;to the design-time document. No Problem!<\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><\/SPAN><\/SPAN>&nbsp;<\/P>\n<P><SPAN><SPAN>You can switch between your design-time and run-time documents easily in the Solution Explorer:<\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/JScript%20Solution%20Explorer.jpg\"><\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><\/SPAN><\/SPAN>&nbsp;<\/P>\n<P><SPAN><SPAN>You can examine an&nbsp;object&#8217;s data&nbsp;when the execution is paused.&nbsp;The type information is much richer than in <A class=\"\" href=\"http:\/\/blogs.msdn.com\/webdevtools\/archive\/2007\/03\/08\/jscript-debugging-in-visual-studio-2005.aspx\">Visual Web Developer 2005<\/A>:<\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><STRONG>Visual Web Developer 2005<\/STRONG>&nbsp;<\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN>&nbsp;<IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/Jscript%20Quick%20Watch.jpg\"><\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><STRONG>Visual Web Developer Orcas<\/STRONG><\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/JScript%20Watch1.jpg\"><\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><\/SPAN><\/SPAN>&nbsp;<\/P>\n<P><SPAN><SPAN>Not only can you see the real types of the objects but also the methods:<\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/JScript%20Watch2.jpg\"><\/SPAN><\/SPAN><SPAN><SPAN><\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><\/SPAN><\/SPAN>&nbsp;<\/P>\n<P><SPAN><SPAN>Plus you can navigate the DOM&nbsp;more easily:<\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/JScript%20Watch3.jpg\"><\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><\/SPAN><\/SPAN>&nbsp;<\/P>\n<P><SPAN><SPAN>Still feel like something is still missing? How about visualizers for reading long text:<\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/JScript%20Visualizer.jpg\"><\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><\/SPAN><\/SPAN>&nbsp;<\/P>\n<P><SPAN><SPAN><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/JScript%20Text%20Visualizer.jpg\"><\/SPAN><\/SPAN><\/P>\n<P><SPAN><SPAN><\/SPAN><\/SPAN>&nbsp;<\/P>\n<P><SPAN><SPAN>Enjoy!<\/SPAN><\/SPAN><\/P><SPAN><SPAN>\n<P class=\"MsoNormal\"><FONT size=\"3\"><STRONG>Barry Tang<\/STRONG><\/FONT><FONT size=\"3\"><STRONG><BR><\/STRONG>Software Design Engineer<BR>Visual Studio Web Tools<\/FONT><\/P>\n<P><\/SPAN><\/SPAN>&nbsp;<\/P>\n<P><SPAN><SPAN><\/SPAN><\/SPAN>&nbsp;<\/P><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Jeff King made a recent post to show off the new JScript IntelliSense&nbsp;feature in the March CTP of Visual Studio. Now I am going to show off the improved JScript Debugging&nbsp;experience in the March CTP. The first thing you will notice is that when you try to debug an IE page, VS will give you [&hellip;]<\/p>\n","protected":false},"author":404,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[4,31,7274,7273,147,7267,7268,7269],"class_list":["post-5104","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aspnet","tag-net","tag-asp-net","tag-jscript","tag-orcas","tag-visual-studio","tag-vwd","tag-web","tag-web-2-0"],"acf":[],"blog_post_summary":"<p>Jeff King made a recent post to show off the new JScript IntelliSense&nbsp;feature in the March CTP of Visual Studio. Now I am going to show off the improved JScript Debugging&nbsp;experience in the March CTP. The first thing you will notice is that when you try to debug an IE page, VS will give you [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/5104","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/404"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=5104"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/5104\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=5104"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=5104"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=5104"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}