Your official information source from the .NET Web Development and Tools group at Microsoft.
Jeff King made a recent post to show off the new JScript IntelliSense feature in the March CTP of Visual Studio. Now I am going to show off the improved JScript Debugging 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 a nice little dialog reminding you to turn on script debugging in IE:
Here is the Advance tab in IE:
After you've turned on script debugging in IE, you can set a breakpoint in your ASPX document right away!
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).
Debug the page (F5) and VS will pause at the breakpoint:
If you look closely, the execution actually paused in the run-time document instead of the design-time document:
You can set breakpoints in the run-time document and they will get saved back to the design-time document. No Problem!
You can switch between your design-time and run-time documents easily in the Solution Explorer:
You can examine an object's data when the execution is paused. The type information is much richer than in Visual Web Developer 2005:
Visual Web Developer 2005
Visual Web Developer Orcas
Not only can you see the real types of the objects but also the methods:
Plus you can navigate the DOM more easily:
Still feel like something is still missing? How about visualizers for reading long text:
Barry TangSoftware Design EngineerVisual Studio Web Tools
This is off topic but....
How come you got that to work on Windows Vista??
I mean, it doesn't install on mine, the download page says Vista is not supported, and Soma confirmed that (said it's because of problem you have with "Red Bits").
And now I see you having it on Vista, any hints on how to have the same.
Hmm... or is that a VPC ?
Instead of what the official word says, and the exlaination I got from from Soma (which is related to having existing VS 2005 I guess), I got it to work on Vista just by installing Expression Web Designer!!!!
Howver, this only applies to my case, there're other different cases on channel9 and msdn forums that I'm not sure how they ended as they were facing different varying errors.
(Yeah, I know. At the end of the day, it's all CTP stuf.)
Sorry for bothering you.
We do test our Orcas builds internally on Windows Vista. The issue with "red bits" that you mentioned is that it is not possible currently with the March CTP to install the correct version of the framework in a public signed release. We have ways to workaround that internally but do not recommend that to customers. This issue is being fixed before Orcas Beta1.
Hope this helps clarify.
You can even debug in present version and use the script explore.I ve used it ,also i used the script debugger in earlier days.The only gotcha i found was i can't step intot he websvc code from the java script although i attached the w3wp .i am not sure if it is a problem in my config or in general.if general can we get the debugger support for this in orcas?what do you say?
In February I did a blog post called My "First Look at Orcas" Presentation . It provided a good summary
only thing i can see as new is the breakpoints and i bet they do a debugger behind the scenes
Una de las preguntas que siempre me han hecho en las presentaciones que he tenido respecto a Ajax es
Una de las preguntas que siempre me han hecho en las presentaciones que he tenido respecto a Ajax es...
Una de las nuevas funcionalidades que nos ofrecerá la nueva versión de Visual Studio es el soporte Intellisense