Visual Studio 2008, 2010, 2011, 2012 Keyboard Shortcuts Keys



It is amazing that you can get around without using a mouse at all. Master the following Visual Studio shortcuts and your colleagues might stare at you with amazement.

1.    F5: Start your project in debug mode


2.    F7 & Shift-F7: Show the code windows & Show the designer window


3.    Alt-Enter: Show the properties panel for a selected object (this is general Windows shortcut that can be used on files and directories)


4.    F6 / Shift-F6 / Ctrl-Shift-B: Build solution / Build project / Build solution


5.    Shift-Alt-C: Add a new class to your project


6.    Ctrl-K + Ctrl-C: Comment a selected block of code


7.    Ctrl-K + Ctrl-U: Un-comment a selected block of code


8.    Ctrl-M + Ctrl-O / Ctrl-M + Ctrl-P: Collapse all code to definitions / Expand all code (stop collapsing)


9.    Ctrl-M + Ctrl+M: Expend or collapse a selected code fragment. The code collapsed depends on where the cursor is located


10.    Ctrl-B + Ctrl-T: Toggle code bookmark


11.    Ctrl-Alt-P: Attach the debugger to a process. This is insanely useful for debugging ASP.NET web sites without having to start the project in debug mode


12.    Ctrl-Alt-L: Show the solution explorer


13.    Ctrl-Shift-A / Alt-Shift-A: Add a new item to your project / add an existing item to your project

The following work in Visual Studio just like they do in most other Windows application.
Ctrl-N: Add a new file
Ctrl-S: Save file
Ctrl-Z / Ctrl-Y: Undo typing / Redo typing
Ctrl-F: Bring up the "Find" dialog
Ctrl-H: Bring up the "Replace" dialog
Ctrl-Tab: Scroll forward through open windows
Ctrl-Shift-Tab: Scroll backwards through open windows




You can follow ...

http://www.dotnet-tricks.com/Tutorial/visualstudio/DEI8040212-Visual-Studio-2008,-2010,-2011,-2012-Keyboard-Shortcuts-Keys.html

or

http://dotnet.dzone.com/news/top-13-visual-studio-keyboard-

Comments

Post a Comment

Popular posts from this blog

Executing PowerShell scripts from C#

Image
Please refer the original post from here http://blogs.msdn.com/b/kebab/archive/2014/04/28/executing-powershell-scripts-from-c.aspx I n today’s post, I will demonstrate the basics of how to execute PowerShell scripts and code from within a C#/.NET applications. I will walk through how to setup your project prerequisites, populate the pipeline with script code and parameters, perform synchronous and asynchronous execution, capture output, and leverage shared namespaces. Update 8/7/2014 : Here is the downloadable solution file. Update 11/5/2014 : Added a section on execution policy behavior. Prerequisites: First, ensure that PowerShell 2.0 or later is installed on the system you are developing on. The features used below will not be supported on PowerShell 1.0. Next, start by making a new console application (targeting .NET 4.0) in Visual Studio. In the solution explorer, add a project reference to the System.Management.Automation assembly * . On my machine (PowerShe...
Read more

HOW TO Use the NumericUpDown Control

HOW TO Use the NumericUpDown Control  Great help taken from  http://www.asp.net/ajaxlibrary/HOW%20TO%20Use%20the%20NumericUpDown%20Control.ashx NumericUpDown Demonstration NumericUpDown Description NumericUpDown is an ASP.NET AJAX extender that can be attached to an ASP.NET TextBox control to add "up" and "down" buttons that increment and decrement the value in the TextBox. The increment and decrement can be simple +1/-1 arithmetic, they can cycle through a provided list of values (like the months of the year), or they can call a Web Service to determine the next value. Page authors can also provide custom images to be used instead of the default up/down button graphics. Video - How Do I: Use the ASP.NET AJAX NumericUpDown Control? NumericUpDown Client Code Sample view plain copy to clipboard print ? < script   runat = "server" >        [System.Web.Services.W...
Read more

Exposing Agile Software Development Myths

Agile development is a movement that started 11 years ago and now is a commonplace discussion for software development teams. Prior to the signing of the Agile Manifesto in Utah in 2001 [endnote 1], the world was using a phased methodology called “Waterfall,” introduced (but not named) by Winston W. Royce [2], ironically trying to explain why that methodology was a bad idea. The methodology forced the completion of a phase in order to continue with the next one. That caused some problems since, no matter how hard the developers tried to gather all requirements and create a full system design, there was always the need in the following phases to go back and change things. Those regressions had a big impact on cost. The Agile principles tried to eliminate all the rigidity of Waterfall by focusing on more productive tasks, like working code over comprehensive documentation, adding more customer collaboration, enforcing individual interactions instead of tools and being a...
Read more