Microsoft keeps adding interesting new controls to the Visual Studio toolbox, but John Mueller regrets to report that many developers don’t even know that those controls exist. Also, every programmer wants to create applications that are free of bugs. In this article, Peter Aitken explores the debugging tools available in Visual Studio.
Gaining Control Over the Visual Studio 2005 Toolbox; Debugging
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
It’s true that the property grid control is not something you would use every day. But when you need it, it’s a life saver and so incredibly easy to use.
Absolutely rock in VS 2005, I cannot stand debugging in 2003 now as I’ve gotten so acustomed to them.
Sidenote: On my VS2k3/5 installs step over is F10 and step into is F11. I think he got confused with VS6.0 which IIRC is indeed F8.
On my VS2k3/5 installs step over is F10 and step into is F11. I think he got confused with VS6.0 which IIRC is indeed F8.
You configure the IDE when you first run it. F10/F11 are the defaults, but you can set it up to work like older IDEs (i.e. F8/F9)
Why would a ASP .net developer need to know about the majority of the controls mentioned in the first article? 9 of the 11 controls are Windows Forms controls. An ASP .net developer would never use them.
I’m a Windows .net form application developer myself and I’m sure there are many ASP controls that I’ve never heard of that an ASP developer would use everyday. Does that make me any less of a developer, just because I don’t know about something irrelevant to what I do?
Whilst both articles are informative and interesting, the first article should not have suggested that all VS developers should know about the controls they featured.