转载一篇VS2008的小技巧，提高工作效率必备啊！

r囧r小猫 2022-12-20 01:48 140阅读 0赞

###### 原文：[http://blogs.msdn.com/johnwpowell/archive/2008/03/23/10-tips-to-boost-your-productivity-with-c-and-visual-studio-2008.aspx][http_blogs.msdn.com_johnwpowell_archive_2008_03_23_10-tips-to-boost-your-productivity-with-c-and-visual-studio-2008.aspx] ######

##### Learn Key Bindings #####

It's an obvious and trivial thing, but the timesaving will add up, especially for those actions you perform tens or hundreds of times a day such as building and debugging.  Here are some basic bindings every Visual Studio developer should know:

*  Build: **CTRL** \+ **SHIFT** \+ **B**
 *  Word completion: **CTRL** \+ **SPACE**
 *  Start with debugging: **F5**
 *  Start without debugging: **CTRL** \+ **F5**

*Even expert Visual Studio developers can benefit by learning new bindings*. Download the [Visual C\# 2008 Keybinding Reference Poster][Visual C_ 2008 Keybinding Reference Poster] and hang it in your work area.

##### Generate XML Comments with GhostDoc #####

Instead of typing XML comments by hand, let a tool do the work for you. Although macros and snippets are reasonably effective for this, I would recommend [Ghost Doc][] over any other solution. This *free* add-in uses customizable templates to generate consistent, English-readable documentation based on the current context.  To use it, right-click (or use CTRL + SHIFT + D) to document the current element.  For example:

[![image][]][image 1]

This generates the following documentation (note GhostDoc split the property name into words and created a sentence from it):

[![image][image 2]][image_image 2]

##### Auto-Implement Properties #####

Take advantage of a new feature of C\#: [auto-implemented properties][]. Rather than creating a private backing field for your properties, let the compiler do it for you. The following demonstrates the syntax:

[![image][image 3]][image_image 3]

Use the code snippet to make this even faster.  Type **prop** (the shortcut for an auto-implemented property) followed by **TAB** **TAB**.  Then fill in the data type and property name:

[![image][image 4]][image_image 4]

##### Refactor #####

The refactor feature in Visual Studio is indispensable for many tasks, especially renaming, but one productivity feature I particularly like is *Encapsulate Field*. If you are unable to use an auto-implemented property, declare a private field and let Visual Studio generate the Property for you.  To use this feature, right-click on the field and select *Refactor* > *Encapsulate Field...*

[![image][image 5]][image_image 5]

The property is created for you:

[![image][image 6]][image_image 6]

##### Add Commands to Visual Studio 2008 #####

Install the [PowerCommands for Visual Studio 2008][] to add several productivity commands such as:

*  Close all documents
 *  Copy and paste a class (automatically renames)
 *  Remove and sort using statements project-wide
 *  Copy and paste references (including a project reference)

Install the [Team Foundation Server Power Tools][] to add several TFS productivity commands such as:

*  Find in source control
 *  Open source folder in Windows Explorer
 *  Work item templates (can be used to set values on multiple work items at once)

Add your own productivity commands.  For example, to add [Reflector][] so it automatically opens on the current project.

*  Select Tools > External Tools
 *  Click Add
 *  Name it Reflector and browse to the executable
 *  Enter $(TargetPath) for the Arguments

#####  #####

##### Speed up Compilation with Project Configuration #####

You may build tens of times during a programming session, so don't enable anything that isn't absolute necessary such as code analysis and XML documentation.  Develop in Debug configuration, and switch to Release configuration just before check-in to run code analysis and generate XML documentation. In a large solution I recently worked on, this shaved a minute off compilation time.

The following shows code analysis *disabled* in Debug configuration:

[![image][image 7]][image_image 7]

The following shows code analysis *enabled* in Release configuration:

[![image][image 8]][image_image 8]

##### Let Visual Studio Generate Unit Test Code #####

Although it can't fully automate unit testing yet (check out [Pex][]), Visual Studio does a good job of generating [positive unit test][] code to give you a jump start.  To use this feature, right-click on an element you would like to test and select *Create Unit Tests... *

[![image][image 9]][image_image 9]

Visual Studio generates the following test method:

[![image][image 10]][image_image 10]

##### Use Interface-Driven-Design #####

You probably never thought of an interface as a productivity feature, but it can be if your development process is driven by contracts instead of implementation.  Let me illustrate with a simplified example.  One developer owns the business layer and another developer owns the data access layer, and they need to agree on how to communicate to implement a new feature.  In some business object designs, business components will instantiate data components (or call a static method).  This is a problem from a design standpoint because the two become tightly coupled.  It is also a problem from the productivity standpoint because the business layer developer becomes dependent on the data access layer developer's implementation.  *Interface-driven design (IDD) solves this issue*.

Rather than the business component developer waiting on the data component developer, they meet to design and implement the interface.  Both developers are then free to go their separate ways and implement the components in parallel.  IDD also enables the business developer to mock the data access component, thereby removing any scheduling dependencies.  The following illustrates the design:

[![image][image 11]][image_image 11]

##### Make a Mockery of Dependencies #####

Different developers may own layers or features that your component is dependent on, but don't let that slow you down.  Suppose you are responsible for the business layer which depends on the data access layer which in turn depends on database tables and stored procedures. Rather than waiting for dependent layers to be completed, mock the data access layer so you can implement and unit test the business layer. By the way, you should be using mocks anyway; otherwise your unit tests are more than likely integration tests.  I recommend [Rhino Mocks][].

Here is a sample unit test with mocks:

[![image][image 12]][image_image 12]

##### Data Drive Unit Tests #####

If you have a unit test that multiple inputs to fully test, you *could* write a test method for every possible combination, but data-driven unit tests are more efficient.  When the unit test is run, it loads data from a table and calls the unit test for each row.  You can access the data in the current row using the TestContext.DataRow property.

[![image][image 13]][image_image 13]

Once the test completes, you can view the results:

[![image][image 14]][image_image 14]

Published Sunday, March 23, 2008 12:48 PM by [johnwpowell][]

Filed under: [Unit Test][], [Visual Studio][]

[http_blogs.msdn.com_johnwpowell_archive_2008_03_23_10-tips-to-boost-your-productivity-with-c-and-visual-studio-2008.aspx]: http://blogs.msdn.com/johnwpowell/archive/2008/03/23/10-tips-to-boost-your-productivity-with-c-and-visual-studio-2008.aspx
[Visual C_ 2008 Keybinding Reference Poster]: http://www.microsoft.com/downloads/details.aspx?familyid=E5F902A8-5BB5-4CC6-907E-472809749973&displaylang=en
[Ghost Doc]: http://www.roland-weigelt.de/ghostdoc/
[image]: /images/20221120/c1b52c30b61a4df9bb03ebb0080a0ca3.png
[image 1]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_2.png
[image 2]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_thumb_1.png
[image_image 2]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_4.png
[auto-implemented properties]: http://msdn2.microsoft.com/en-us/library/bb384054.aspx
[image 3]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_thumb_2.png
[image_image 3]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_6.png
[image 4]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_thumb_14.png
[image_image 4]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_30.png
[image 5]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_thumb_3.png
[image_image 5]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_8.png
[image 6]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_thumb_4.png
[image_image 6]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_10.png
[PowerCommands for Visual Studio 2008]: http://code.msdn.microsoft.com/PowerCommands
[Team Foundation Server Power Tools]: http://msdn2.microsoft.com/en-us/tfs2008/bb980963.aspx
[Reflector]: http://www.aisto.com/roeder/dotnet/
[image 7]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_thumb_5.png
[image_image 7]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_12.png
[image 8]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_thumb_6.png
[image_image 8]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_14.png
[Pex]: http://research.microsoft.com/projects/Pex/
[positive unit test]: http://en.wikipedia.org/wiki/Test-driven_development
[image 9]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_thumb_7.png
[image_image 9]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_16.png
[image 10]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_thumb_8.png
[image_image 10]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_18.png
[image 11]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_thumb_11.png
[image_image 11]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_24.png
[Rhino Mocks]: http://ayende.com/projects/rhino-mocks.aspx
[image 12]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_thumb_10.png
[image_image 12]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_22.png
[image 13]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_thumb_12.png
[image_image 13]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_26.png
[image 14]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_thumb_13.png
[image_image 14]: http://blogs.msdn.com/blogfiles/johnwpowell/WindowsLiveWriter/10TipstoBoostYourProductivitywithCandVis_753E/image_28.png
[johnwpowell]: http://blogs.msdn.com/user/Profile.aspx?UserID=122016
[Unit Test]: http://blogs.msdn.com/johnwpowell/archive/tags/Unit+Test/default.aspx
[Visual Studio]: http://blogs.msdn.com/johnwpowell/archive/tags/Visual+Studio/default.aspx