(Note: This blog post was originally published under my old domain(codesmiles.com), here. Web Archive link. I have recently realised how folks get significantly uncomfortable and could also loose little amount of productivity speed when navigating Solution Explorer which is in a state of mess due to randomly expanded and collapsed Solution Explorer items, it surely causes at least a tiny amount of lack of clarity. The basic TreeView control or Tree control is a common windows control found in many places in Windows OS, including Windows Explorer. The same is found in Visual Studio’s Solution Explorer, for those who are not aware; this control supports some keyboard shortcuts, I mean whether you are in Windows Explorer or Visual Studio Solution Explorer you can select a node’s parent and use these shortcuts. + (plus) –> Expand – (minus) –> Collapse * (asterick) –> If you would like to expand recursively a particular item’s child items But there is no shortcut to collapse recursively. Collapse Selection in Solution Explorer extension is available for Visual Studio 2010 that adds an icon to the Solution Explorer(shown below), clicking which recursively collapses the child items. You can press Ctrl + Alt + Num(-) – numeric
Tag: visual studio 2010
Visual Studio 2010 New Features in Debugging – Exciting & Innovative
(Note: This blog post was originally published under my old domain(codesmiles.com), here. Web Archive link. (This post is part of my Visual Studio 2010 series) This article talks about Visual Studio 2010’s new features related to debugging, applicable from beginner to expert(based on Visual Studio 2010 beta 2). Visual Studio 2010 comes with powerful debugging features. Debugging is an area where an improvement brings great relief to developers, and increases developer happiness. Visual Studio 2010 seems to highly enhance debugging support, and can change some basic ways we used to debug applications, let us have a look.[more] Export/Import Breakpoints By using Export/Import breakpoints in Visual Studio 2010, you can debug a portion of the application and export the current set of breakpoints and import it back whenever you want to debug the same portion of application, no matter what breakpoints you have currently placed in your code. This feature will enable you to have different set of breakpoints for each scenario or portion of application that you may need to debug. This is one of the features that I highly wished to have. An example scenario… consider your web page/windows form has basic CRUD(Create/Read/Update/Del) options, you are currently working on