Merge branch 'master' into gewarren-install

Author: mikeblome

docs/ide/TOC.md

@@ -113,16 +113,18 @@
 ### [JavaScript IntelliSense](javascript-intellisense.md)
 ### [Visual C++ Intellisense](visual-cpp-intellisense.md)
 ### [Supplying XML Code Comments](supplying-xml-code-comments.md)
+## [Navigating Your Code](navigating-code.md)
+### [Finding references in your code](finding-references.md)
+### [Go To Definition and Peek Definition](go-to-and-peek-definition.md)
+### [How to: View and Edit Code by Using Peek Definition (Alt+F12)](how-to-view-and-edit-code-by-using-peek-definition-alt-plus-f12.md)
+### [Find code using Go To commands](go-to.md)
 ## [Customizing the Editor](customizing-the-editor.md)
 ### [How to: Change Text Case in the Editor](how-to-change-text-case-in-the-editor.md)
 ### [How to: Manage Editor Modes](how-to-manage-editor-modes.md)
 ### [How to: Manage Editor Windows](how-to-manage-editor-windows.md)
 ## [Develop code in Visual Studio without projects or solutions](develop-code-in-visual-studio-without-projects-or-solutions.md)
 ## [Create portable, custom editor settings with EditorConfig](create-portable-custom-editor-options.md)
 ## [How to: Track Your Code by Customizing the Scrollbar](how-to-track-your-code-by-customizing-the-scrollbar.md)
-## Navigating Your Code
-### [Go To](go-to.md)
-### [How to: View and Edit Code by Using Peek Definition (Alt+F12)](how-to-view-and-edit-code-by-using-peek-definition-alt-plus-f12.md)
 ## [Code Snippets](code-snippets.md)
 ### [Walkthrough: Creating a Code Snippet](walkthrough-creating-a-code-snippet.md)
 ### [How to: Distribute Code Snippets](how-to-distribute-code-snippets.md)

docs/ide/finding-references.md

@@ -0,0 +1,48 @@
+---
+title: "Finding references in your code | Microsoft Docs"
+ms.custom: ""
+ms.date: "09/26/2017"
+ms.reviewer: ""
+ms.suite: ""
+ms.technology: 
+  - "vs-ide-general"
+ms.tgt_pltfrm: ""
+ms.topic: "article"
+helpviewer_keywords:
+  - "code editor, find all references"
+  - "find all references"
+author: "gewarren"
+ms.author: "gewarren"
+manager: "ghogen"
+---
+# Finding references in your code  
+You can use the **Find All References** command to find where particular code elements are referenced throughout your codebase. The **Find All References** command is available on the context (right-click) menu of the element you want to find references to. Or, if you are a keyboard user, press **Shift + F12**.  
+
+The results appear in a tool window named **'*element*' references**, where *element* is the name of the item you are searching for. A toolbar in the **references** window enables you to:  
+- Change the scope of the search in a drop-down list box. You can choose to look only in changed documents all the way up to the entire solution.  
+- Copy the selected referenced item by choosing the **Copy** button.  
+- Choose buttons to go to the next or previous location in the list, or press the **F8** and **Shift + F8** keys to do so.  
+- Remove any filters on the returned results by choosing the **Clear All Filters** button.  
+- Change how returned items are grouped by choosing a setting in the **Group by:** drop-down list box.  
+- Keep the current search results window by choosing the **Keep Results** button. When you choose this button, the current search results stay in this window, and new search results appear in a new tool window.  
+- Search for strings within the search results by entering text in the **Search Find All References** text box.  
+
+You can also hover the mouse over any search result to see a preview of the reference.  
+
+![Find All References tool window](../ide/media/vside_findallreferences.png)  
+
+### Navigate to references
+You can use the following methods to navigate to references in the **references** window:  
+
+- Press **F8** to go to the next reference, or **Shift + F8** to go to the previous reference.  
+- Press the **Enter** key on a reference, or double-click it, to go to it in code.  
+- On the context menu of a reference, choose the **Go To Previous Location** or **Go To Next Location** commands.  
+- Choose the **UP arrow** and **DOWN arrow** keys (if they are enabled in the Options dialog box). To enable this functionality, on the menu bar, choose **Tools**, **Options**, **Environment**, **Tabs and Windows**, **Preview Tab**, and then select the **Allow new files to be opened in the preview tab** and **Preview selected files in Find Results** boxes.  
+
+### Change reference groupings  
+By default, references are grouped by project, then by definition. However, you can change this grouping order by changing the setting in the **Group by:** drop-down list box on the toolbar. For example, you can change it from the default setting of **Project then definition** to **Definition then project**, as well to other settings.  
+
+**Definition** and **Project** are the two default groupings used, but you can add others by choosing the **Grouping** command on the selected item's context menu. Adding more groupings can be helpful if your solution has a lot of files and paths.  
+
+## See also  
+[Navigating Code](../ide/navigating-code.md)  

docs/ide/go-to-and-peek-definition.md

@@ -0,0 +1,50 @@
+---
+title: "Go To Definition and Peek Definition | Microsoft Docs"
+ms.custom: ""
+ms.date: "09/26/2017"
+ms.reviewer: ""
+ms.suite: ""
+ms.technology: 
+  - "vs-ide-general"
+ms.tgt_pltfrm: ""
+ms.topic: "article"
+helpviewer_keywords:
+  - "code editor, go to definition"
+  - "code editor, peek definition"
+  - "go to definition"
+  - "peek definition"
+author: "gewarren"
+ms.author: "gewarren"
+manager: "ghogen"
+---
+# Go To Definition and Peek Definition  
+The Go To Definition and Peek Definition features enable you to easily view the definition of a type or member.
+
+## Go To Definition  
+The Go To Definition feature navigates to the source of a type or member, and opens the result in a new tab. If you are a keyboard user, place your text cursor somewhere inside the symbol name and press **F12**. If you are a mouse user, either select **Go To Definition** from the context menu, or, use the **Ctrl-click** functionality described below.  
+
+### Ctrl-click Go To Definition  
+New for Visual Studio 2017 version 15.4 is an easier way for mouse users to quickly access Go To Definition. Symbols become clickable when you press **Ctrl** and hover over the type or member. To quickly navigate to the definition of a symbol, press the **Ctrl** key and then click on it. It's that easy!
+
+![Mouse click go to definition animation](../ide/media/click_gotodef.gif)
+
+You can change the modifier key for mouse-click **Go To Definition** by going to **Tools**, **Options**, **Text Editor**, **General**, and selecting either **Alt** or **Ctrl+Alt** from the **Use modifier key** drop-down. You can also disable mouse-click **Go To Definition** by unchecking the **Enable mouse click to perform Go To Definition** checkbox.  
+
+![Enabling mouse-click go to definition](../ide/media/editor_options_mouse_click_gotodef.png)  
+
+## Peek Definition
+The Peek Definition feature lets you preview the definition of a type without leaving your current location in the editor. If you are a keyboard user, place your text cursor somewhere inside the type or member name and press **Alt + F12**. If you are a mouse user, either select **Peek Definition** from the context menu, or, in Visual Studio 2017 version 15.4 and later, there is an additional way to peek view a definition by using the mouse. First, go to **Tools**, **Options**, **Text Editor**, **General**. Select the option **Open definition in peek view** and click **OK** to close the **Options** dialog box.  
+
+![Setting the mouse-click peek definition option](../ide/media/editor_options_peek_view.png)  
+
+Then, press **Ctrl** (or whichever modifier key is selected in **Options**), and click on the type or member.  
+
+![Peek definition animation](../ide/media/peek_definition.gif)
+
+If you peek another definition from the popup window, you will start a breadcrumb path which you can navigate using the circles and arrows which appear above the popup.  
+
+For more information, see [How to: View and Edit Code by Using Peek Definition (Alt+F12)](how-to-view-and-edit-code-by-using-peek-definition-alt-plus-f12.md).  
+
+## See Also  
+[Navigating Code](../ide/navigating-code.md)  
+[How to: View and Edit Code by Using Peek Definition (Alt+F12)](how-to-view-and-edit-code-by-using-peek-definition-alt-plus-f12.md)  

docs/ide/go-to.md

@@ -1,125 +1,83 @@
 ---
-title: "Go To | Microsoft Docs"
+title: "Find code using Go To commands | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/16/2016"
+ms.date: "09/26/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
   - "vs-ide-general"
 ms.tgt_pltfrm: ""
 ms.topic: "article"
 ms.assetid: 509b2107-23d1-4fb3-987f-ab99ef45b72e
+helpviewer_keywords:
+  - "code editor, go to"
+  - "code editor, go to line"
+  - "go to line"
+  - "go to"
 author: "gewarren"
 ms.author: "gewarren"
 manager: "ghogen"
-translation.priority.ht: 
-  - "cs-cz"
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "pl-pl"
-  - "pt-br"
-  - "ru-ru"
-  - "tr-tr"
-  - "zh-cn"
-  - "zh-tw"
 ---
+# Find code using Go To commands  
+Visual Studio's **Go To** commands perform a focused search of your code to help you quickly find specified items. You can go to a specific line, type, symbol, file, and member from a simple, unified interface. This feature exists in Visual Studio 2017 and later.  
 
-# Go To
-There are many ways to easily navigate your code inside of the Visual Studio IDE, both from the keyboard and the mouse.
+### How to use it  
 
-<!-- VERSIONLESS -->
-## Go To All
-This feature exists in Visual Studio 2017 and later.  It allows you to navigate through your code to find the specific bits you are looking for.  You can search for a specific line, type, symbol, file, and more from a simple, unified interface.
-
-### How to use
-* **Keyboard**
-  * Press **Ctrl+,** or **Ctrl+T**.  (Note that your keyboard shortcut may be different based on which profile you've selected.)
-* **Mouse**
-  * Select **Edit > Go To > Go To All**.
+Input        | Function 
+------------ | ---
+**Keyboard** | Press **Ctrl + T**  
+**Mouse**    | Select **Edit**, **Go To**, **Go To All**  
 
-This will display a small window at the top right of your IDE, by default.
+This will display a small window at the top right of your code editor, by default.  
 
 ![Go To All](media/gotoall.png)
 
-From here, there are several ways to proceed:
-* Enter text without a prefix to search using the [filter icons](#filtered-searches) selected below the text box.
-* Enter a [prefix](#filtered-searches) followed by the text to search.
-* Enter a question mark (?) to get additional help.
+As you type in the text box, the results appear in a drop-down list below the text box. To go to an element, choose it in the list.    
+
+![Navigate To window](../ide/media/vside_navigatetowindow.png "Navigate To window")  
+
+You can also enter a question mark (?) to get additional help.  
+
   ![Go To All Help](media/gotoall_help.png)
 
-### Filtered Searches
-To narrow your search to a specific type, you can either use a prefix when typing, or use the icons below the search window as shown below.
+### Filtered Searches  
+By default, the specified item is searched for in all solution items. However, you can limit your code search to specific element types by prefacing the search terms with certain characters. You can also quickly change the search filter by choosing buttons on the Go To dialog box toolbar. Buttons that change the type filters are on the left side, and buttons that change the scope of the search are on the right side.  
+
+![Go to members](../ide/media/vside_navigation_toolbar.png)
+
+#### Filter to a specific type of code element  
+To narrow your search to a specific type of code element, you can either specify a prefix in the search box, or select one of the five filter icons:  
 
 Prefix | Icon | Shortcut | Description
 :----: | ---- | -------- | ---
-#      | ![Symbol Icon](media/gotoall_symbolicon.png) | Ctrl+1, Ctrl+S | Find matching symbols
-f      | ![File Icon](media/gotoall_fileicon.png)     | Ctrl+1, Ctrl+F | Find matching file names
-m      | ![Member Icon](media/gotoall_membericon.png) | Ctrl+1, Ctrl+M | Find matching members
-t      | ![Type Icon](media/gotoall_typeicon.png)     | Ctrl+1, Ctrl+T | Find matching types
-:      | ![Line Icon](media/gotoall_lineicon.png)     | Ctrl+G         | Go to the line number entered
+\#      | ![Symbol Icon](media/gotoall_symbolicon.png) | Ctrl+1, Ctrl+S | Go to the specified symbol
+f      | ![File Icon](media/gotoall_fileicon.png)     | Ctrl+1, Ctrl+F | Go to the specified file
+m      | ![Member Icon](media/gotoall_membericon.png) | Ctrl+1, Ctrl+M | Go to the specified member
+t      | ![Type Icon](media/gotoall_typeicon.png)     | Ctrl+1, Ctrl+T | Go to the specified type
+:      | ![Line Icon](media/gotoall_lineicon.png)     | Ctrl+G         | Go to the specified line number
 
-### Search Locations
-To narrow your search to specific locations, use the two document icons.
+#### Filter to a specific location    
+To narrow your search to a specific location, select one of the two document icons:  
 
 Icon | Description
 ---- | ---
 ![Current Document](media/gotoall_currentdocument.png) | Search current document only
-![External Documents](media/gotoall_external.png) | Search external documents in addition to those located in the project/solution
+![External Documents](media/gotoall_external.png) | Search external documents in addition to those located in the project/solution  
 
-### Settings
-Clicking the gear icon ![Gear Icon](media/gotoall_gear.png) at the lower-right lets you change how this feature works.
+### Camel casing  
+If you use [camel casing](https://en.wikipedia.org/wiki/Camel_case) in your code, you can find code elements faster by entering only the capital letters of the code element name. For example, if your code has a type called `CredentialViewModel`, you can narrow down the search by choosing the Type filter ("t") and then entering just the capital letters of the name (`CVM`) in the Go To dialog box. This feature can be helpful if your code has long names.  
+
+![Navigate To window - searching with capitals](../ide/media/vside_capitalsearch.png)
+
+### Settings  
+Selecting the gear icon ![Gear Icon](media/gotoall_gear.png) lets you change how this feature works:  
 
 Setting | Description
 ------- | ---
 Use preview tab | Display the selected item immediately in the IDE's preview tab
-Show details    | Display project, file, line and summary information from documentation comments in the window
-Center window   | Move this window to the center of the IDE instead of the top-right
-<!-- END VERSIONLESS -->
-
-## Go To Definition
-Navigate to the source of a type and open the result in a new tab:
-
-Input        | Function 
------------- | ---
-**Keyboard** | Place your text cursor somewhere inside the type name, and press **F12**
-**Mouse**    | Right-click on the type name and select **Go To Definition**
-
-## Peek Definition
-Preview the definition of a type in a popup window instead of a new tab:
-
-Input        | Function 
------------- | ---
-**Keyboard** | Place your text cursor somewhere inside the type name, and press **Alt+F12**
-**Mouse**    | Right-click on the type name and select **Peek Definition**
-
-If you peek another definition from the popup window, you will start a breadcrumb path which you can navigate using the circles and arrows which appear above the popup.  For more information, see [How to: View and Edit Code by Using Peek Definition (Alt+F12)](how-to-view-and-edit-code-by-using-peek-definition-alt-plus-f12.md).
-
-## Go To Implementation
-Navigate from a base class or type to its implementations.  If there are multiple implementations, you will see them listed in the **Find Symbol Results** window:
-
-Input        | Function 
------------- | ---
-**Keyboard** | Place your text cursor somewhere inside the type name, and press **Ctrl+F12**
-**Mouse**    | Right-click on the type name and select **Go To Implementation**
-
-## Find All References
-Find all places where a method/property/variable is being used.  You can use this to verify dead code and check possible side-effects of a large refactoring.  Press **F8** to jump between results.
-
-Input        | Function 
------------- | ---
-**Keyboard** | Place your text cursor somewhere inside the type name, and press **Ctrl+K, R**
-**Mouse**    | Right-click on the type name and select **Find All References**
-
-## Navigating Results
-When using the navigation features of Visual Studio, you can navigate forward and backward through the stack:
-
-Input        | Function 
------------- | ---
-**Ctrl+-**          | Navigate backward through the stack
-**Ctrl+Shift+-**    | Navigate forward through the stack
+Show details    | Display project, file, line, and summary information from documentation comments in the window
+Center window   | Move this window to the top-center of the code editor, instead of the top-right   
 
-You can also use the **View > Navigate Backward** and **View > Navigate Forward** menu items.
+## See Also  
+[Navigating Code](../ide/navigating-code.md)  
+[Go To Definition and Peek Definition](../ide/go-to-and-peek-definition.md)