Merge pull request #3826 from MicrosoftDocs/master

Daily publishing Feb.5

Author: JiayueHu

docs/containers/docker-tools.md

@@ -7,6 +7,7 @@ ms.date: 02/01/2019
 ms.prod: visual-studio-dev15
 ms.technology: vs-azure
 ms.topic: include
+monikerRange: ">= vs-2017"
 ---
 # Quickstart: Visual Studio Tools for Docker
 

docs/debugger/allocation-hooks-and-c-run-time-memory-allocations.md

@@ -2,14 +2,14 @@
 title: "Allocation Hooks and C Run-Time Memory Allocations | Microsoft Docs"
 ms.date: "11/04/2016"
 ms.topic: "conceptual"
-f1_keywords: 
+f1_keywords:
   - "vs.debug.hooks"
-dev_langs: 
+dev_langs:
   - "CSharp"
   - "VB"
   - "FSharp"
   - "C++"
-helpviewer_keywords: 
+helpviewer_keywords:
   - "debugging [C++], hook functions"
   - "memory allocation, troubleshooting allocation hooks"
   - "allocation hooks"
@@ -18,20 +18,20 @@ ms.assetid: cc34ee96-3d91-41bd-a019-aa3759139e7e
 author: "mikejo5000"
 ms.author: "mikejo"
 manager: jillfra
-ms.workload: 
+ms.workload:
   - "multiple"
 ---
 # Allocation Hooks and C Run-Time Memory Allocations
-A very important restriction on allocation hook functions is that they must explicitly ignore `_CRT_BLOCK` blocks. These blocks are the memory allocations made internally by C run-time library functions if they make any calls to C run-time library functions that allocate internal memory. You can ignore `_CRT_BLOCK` blocks by including the following code at the beginning of your allocation hook function:  
-  
+A very important restriction on allocation hook functions is that they must explicitly ignore `_CRT_BLOCK` blocks. These blocks are the memory allocations made internally by C run-time library functions if they make any calls to C run-time library functions that allocate internal memory. You can ignore `_CRT_BLOCK` blocks by including the following code at the beginning of your allocation hook function:
+
 ```cpp
-if ( nBlockUse == _CRT_BLOCK )  
-    return( TRUE );  
-```  
-  
- If your allocation hook doesn't ignore `_CRT_BLOCK` blocks, then any C run-time library function called in your hook can trap the program in an endless loop. For example, `printf` makes an internal allocation. If your hook code calls `printf`, then the resulting allocation will cause your hook to be called again, which will call **printf** again, and so on, until the stack overflows. If you need to report `_CRT_BLOCK` allocation operations, one way to circumvent this restriction is to use Windows API functions, rather than C run-time functions, for formatting and output. Because the Windows APIs don't use the C run-time library heap, they won't trap your allocation hook in an endless loop.  
-  
- If you examine the run-time library source files, you will see that the default allocation hook function, **CrtDefaultAllocHook** (which simply returns **TRUE**), is located in a separate file of its own, DBGHOOK.C. If you want your allocation hook to be called even for the allocations made by the run-time startup code that is executed before your application's **main** function, you can replace this default function with one of your own, instead of using [_CrtSetAllocHook](/cpp/c-runtime-library/reference/crtsetallochook).  
-  
-## See Also  
- [Debug Hook Function Writing](../debugger/debug-hook-function-writing.md)   
+if ( nBlockUse == _CRT_BLOCK )
+    return( TRUE );
+```
+
+If your allocation hook doesn't ignore `_CRT_BLOCK` blocks, then any C run-time library function called in your hook can trap the program in an endless loop. For example, `printf` makes an internal allocation. If your hook code calls `printf`, then the resulting allocation will cause your hook to be called again, which will call **printf** again, and so on, until the stack overflows. If you need to report `_CRT_BLOCK` allocation operations, one way to circumvent this restriction is to use Windows API functions, rather than C run-time functions, for formatting and output. Because the Windows APIs don't use the C run-time library heap, they won't trap your allocation hook in an endless loop.
+
+If you examine the run-time library source files, you will see that the default allocation hook function, **CrtDefaultAllocHook** (which simply returns **TRUE**), is located in a separate file of its own, DBGHOOK.C. If you want your allocation hook to be called even for the allocations made by the run-time startup code that is executed before your application's **main** function, you can replace this default function with one of your own, instead of using [_CrtSetAllocHook](/cpp/c-runtime-library/reference/crtsetallochook).
+
+## See Also
+[Debug Hook Function Writing](../debugger/debug-hook-function-writing.md)

docs/deployment/deploying-applications-services-and-components.md

@@ -25,7 +25,7 @@ ms.workload:
   - "multiple"
 ---
 
-# Quickstart: First look at deployment in Visual Studio
+# First look at deployment in Visual Studio
 
 By deploying an application, service, or component, you distribute it for installation on other computers, devices, or servers, or in the cloud. You choose the appropriate method in Visual Studio for the type of deployment that you need. (Many app types support other deployment tools such as command line deployment or NuGet that are not described here.)
 

docs/extensibility/debugger/reference/idebugloadcompleteevent2.md

@@ -27,10 +27,7 @@ IDebugLoadCompleteEvent2 : IUnknown
 
 ## Notes for Callers  
  The DE creates and sends this event object to report that a program has been successfully loaded. The event is sent by using the [IDebugEventCallback2](../../../extensibility/debugger/reference/idebugeventcallback2.md) callback function that is supplied by the SDM when it attached to the program being debugged.  
-  
-## Remarks  
- This event is a stopping event and must have the `EVENT_STOPPING` flag set on the event attributes.  
-  
+   
 ## Requirements  
  Header: msdbg.h  
 
@@ -41,4 +38,4 @@ IDebugLoadCompleteEvent2 : IUnknown
 ## See Also  
  [Core Interfaces](../../../extensibility/debugger/reference/core-interfaces.md)   
  [IDebugEvent2](../../../extensibility/debugger/reference/idebugevent2.md)   
- [IDebugEventCallback2](../../../extensibility/debugger/reference/idebugeventcallback2.md)
+ [IDebugEventCallback2](../../../extensibility/debugger/reference/idebugeventcallback2.md)

docs/extensibility/extending-the-output-window.md

@@ -109,7 +109,7 @@ void CreatePane(string title)
     catch (ArgumentException)  
     {  
         // Create a new pane and write to it.  
-        return panes.Add(title);  
+        panes.Add(title);  
     }  
 }  
 ```  

docs/ide/editorconfig-code-style-settings-reference.md

@@ -1384,6 +1384,7 @@ The following list shows the formatting convention rules available in Visual Stu
 - .NET formatting settings
     - [Organize usings](#usings)
         - dotnet_sort_system_directives_first
+        - dotnet_separate_import_directive_groups
 - C# formatting settings
     - [Newline options](#newline)
         - csharp_new_line_before_open_brace
@@ -1426,6 +1427,7 @@ The following table shows the rule name, applicable languages, default value, an
 | Rule name | Applicable languages | Visual Studio default | Visual Studio 2017 version |
 | ----------- | -------------------- | ----------------------| ---------------- |
 | dotnet_sort_system_directives_first | C# and Visual Basic | true | 15.3 |
+| dotnet_separate_import_directive_groups | C# and Visual Basic | true | 15.5 |
 
 **dotnet\_sort\_system\_directives_first**
 
@@ -1454,6 +1456,34 @@ Example *.editorconfig* file:
 dotnet_sort_system_directives_first = true
 ```
 
+**dotnet\_separate\_import\_directive\_groups**
+
+- When this rule is set to **true**, place a blank line between using directive groups.
+- When this rule is set to **false**, do not place a blank line between using directive groups.
+
+Code examples:
+
+```csharp
+// dotnet_separate_import_directive_groups = true
+using System.Collections.Generic;
+using System.Threading.Tasks;
+
+using Octokit;
+
+// dotnet_separate_import_directive_groups = false
+using System.Collections.Generic;
+using System.Threading.Tasks;
+using Octokit;
+```
+
+Example *.editorconfig* file:
+
+```EditorConfig
+# .NET formatting settings:
+[*.{cs,vb}]
+dotnet_separate_import_directive_groups = true
+```
+
 ### C# formatting settings
 
 The formatting rules in this section apply only to C# code.
@@ -2187,6 +2217,7 @@ charset = utf-8-bom
 [*.{cs,vb}]
 # Organize usings
 dotnet_sort_system_directives_first = true
+dotnet_separate_import_directive_groups = false
 
 # this. preferences
 dotnet_style_qualification_for_field = false:none

docs/ide/reference/sync-type-and-file.md

@@ -26,6 +26,9 @@ This refactoring applies to:
 
 **Why:** Placing a type in a file with a different name, or vice-versa, it difficult to find what you're looking for. By renaming either the type or filename, code becomes more readable and easier to navigate.
 
+> [!NOTE]
+> This refactoring is not yet available for .NET Standard and .NET Core projects.
+
 ## How-to
 
 1. Highlight or place the text cursor inside the name of the type to synchronize:
@@ -57,9 +60,6 @@ This refactoring applies to:
 
        ![Inline result Visual Basic](media/synctype-result-vb.png)
 
-> ![NOTE]
-> This refactoring is not yet available for .NET Standard and .NET Core projects.
-
 ## See also
 
 - [Refactoring](../refactoring-in-visual-studio.md)

docs/javascript/TOC.yml

@@ -6,6 +6,8 @@
     href: javascript-in-vs-2017.md
 - name: Quickstarts
   items:
+  - name: First look at the Visual Studio IDE
+    href: quickstart-ide-orientation-js.md
   - name: Create a Node.js project
     href: /visualstudio/ide/quickstart-nodejs?toc=/visualstudio/javascript/toc.json
   - name: Create a Vue.js project

docs/javascript/index.yml

@@ -27,7 +27,7 @@ sections:
       image:
         src: https://docs.microsoft.com/media/common/i_setup.svg
       title: Install Visual Studio
-    - href: ../ide/quickstart-ide-orientation.md
+    - href: ../javascript/quickstart-ide-orientation-js.md
       html: <p></p>
       image:
         src: https://docs.microsoft.com/media/logos/logo_visual-studio.svg

docs/javascript/media/build-output-minimal.png

@@ -0,0 +1,111 @@
+---
+title: Tour of the Visual Studio IDE
+titleSuffix: ""
+ms.date: 02/05/2019
+ms.prod: visual-studio-dev15
+ms.topic: quickstart
+author: mikejo5000
+ms.author: mikejo
+manager: jillfra
+ms.workload:
+  - "multiple"
+---
+# First look at the Visual Studio IDE
+
+In this 5-10 minute introduction to the Visual Studio integrated development environment (IDE), we'll take a tour of some of the windows, menus, and other UI features.
+
+If you haven't already installed Visual Studio, go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2017) page to install it for free.
+
+## Start Page
+
+The first thing you'll see after you launch Visual Studio is most likely the **Start Page**. The **Start Page** is designed as a "hub" to help you find the commands and project files you need faster. The **Recent** section displays projects and folders you've worked on recently. Under **New project**, you can click a link to bring up the **New Project** dialog box, or under **Open**, you can open an existing code project or folder. On the right is a feed of the latest developer news.
+
+![Start Page in Visual Studio](media/start-page.png)
+
+If you close the **Start Page** and want to see it again, you can reopen it from the **File** menu.
+
+![File menu in Visual Studio](media/quickstart-IDE-file-menu-large.png)
+
+## Create a project
+
+To continue exploring Visual Studio's features, let's create a new project.
+
+1. On the **Start Page**, in the search box under **New project**, type in **javascript** to filter the list of project types to those that contain "javascript" in their name or language type.
+
+   ![Search project templates on Visual Studio Start Page](media/start-page-search-templates.png)
+
+   Visual Studio provides various kinds of project templates that help you get started coding quickly. Choose a **Blank Node.js Web Application** project template. (Alternatively, if you're a TypeScript developer, feel free to create a project in that language. The UI we'll be looking at is similar for all programming languages.)
+
+1. In the **New Project** dialog box that appears, accept the default project name and choose **OK**.
+
+   The project is created and a file named *server.cs* opens in the **Editor** window. The **Editor** shows the contents of files, and is where you'll do most of your coding work in Visual Studio.
+
+   ![Editor in Visual Studio](media/editor.png)
+
+## Solution Explorer
+
+**Solution Explorer**, which is typically on the right-hand side of Visual Studio, shows you a graphical representation of the hierarchy of files and folders in your project, solution, or code folder. You can browse the hierarchy and navigate to a file in **Solution Explorer**.
+
+![Solution Explorer in Visual Studio](media/quickstart-IDE-solution-explorer.png)
+
+## Menus
+
+The menu bar along the top of Visual Studio groups commands into categories. For example, the **Project** menu contains commands related to the project you're working in. On the **Tools** menu, you can customize how Visual Studio behaves by selecting **Options**, or add features to your installation by selecting **Get Tools and Features**.
+
+![Menu bar in Visual Studio](media/quickstart-IDE-menu-bar.png)
+
+Let's open the **Error List** window by choosing the **View** menu, and then **Error List**.
+
+## Error List
+
+The **Error List** shows you errors, warning, and messages regarding the current state of your code. If there are any errors (such as a missing brace or semicolon) in your file, or anywhere in your project, they're listed here.
+
+![Error List in Visual Studio](media/quickstart-IDE-error-list.png)
+
+## Output window
+
+The **Output** window shows you output messages from building your project and from your source control provider.
+
+Let's build the project to see some build output. From the **Build** menu, choose **Build Solution**. The **Output** window automatically obtains focus and display a successful build message.
+
+![Output window in Visual Studio](media/build-output-minimal.png)
+
+## Quick Launch
+
+The **Quick Launch** box is a quick and easy way to do pretty much anything in Visual Studio. You can enter some text related to what you want to do, and it'll show you a list of options that pertain to the text. For example, imagine you want to increase the build output's verbosity to display additional details about what exactly build is doing. Here's how you might do that:
+
+1. Type **verbosity** into the **Quick Launch** box. From the displayed results, choose **Projects and Solutions --> Build and Run** under the **Options** category.
+
+   ![Quick launch box in Visual Studio](media/quickstart-IDE-quick-launch.png)
+
+   The **Options** dialog box opens to the **Build and Run** options page.
+
+1. Under **MSBuild project build output verbosity**, choose **Normal**, and then click **OK**.
+
+1. Build the project again by right-clicking on the **NodejsWebApp1** project in **Solution Explorer** and choosing **Rebuild** from the context menu.
+
+   This time the **Output** window shows more verbose logging from the build process, including which files were copied where.
+
+   ![Verbose build output in Visual Studio](media/build-output-verbose.png)
+
+## Send Feedback menu
+
+Should you encounter any problems while you're using Visual Studio, or if you have suggestions for how to improve the product, you can use the **Send Feedback** menu at the top of the Visual Studio window, next to the **Quick Launch** box.
+
+![Send Feedback menu in Visual Studio](../ide/media/quickstart-ide-send-feedback.png)
+
+## Next steps
+
+We've looked at just a few of the features of Visual Studio to get acquainted with the user interface. To explore further:
+
+> [!div class="nextstepaction"]
+> [Learn about the code editor](write-and-edit-code.md)
+
+> [!div class="nextstepaction"]
+> [Learn about projects and solutions](../get-started/tutorial-projects-solutions.md)
+
+## See also
+
+- [Overview of the Visual Studio IDE](../get-started/visual-studio-ide.md)
+- [More features of Visual Studio 2017](../ide/advanced-feature-overview.md)
+- [Change theme and font colors](../ide/quickstart-personalize-the-ide.md)

docs/javascript/media/build-output-verbose.png

@@ -17,7 +17,7 @@ dev_langs:
 ---
 # Walkthrough: Create a Custom Text Template Host
 
-A *text template*<em>host</em> provides an environment that enables the *text template transformation engine* to run. The host is responsible for managing the engine's interaction with the file system. The engine or *directive processor* that needs a file or an assembly can request a resource from the host. The host can then search directories and the global assembly cache to locate the requested resource. For more information, see [The Text Template Transformation Process](../modeling/the-text-template-transformation-process.md).
+A *text template host* provides an environment that enables the *text template transformation engine* to run. The host is responsible for managing the engine's interaction with the file system. The engine or *directive processor* that needs a file or an assembly can request a resource from the host. The host can then search directories and the global assembly cache to locate the requested resource. For more information, see [The Text Template Transformation Process](../modeling/the-text-template-transformation-process.md).
 
 You can write a custom host if you want to use the *text template transformation* functionality from outside Visual Studio or if you want to integrate that functionality into custom tools. To create a custom host, you must create a class that inherits from <xref:Microsoft.VisualStudio.TextTemplating.ITextTemplatingEngineHost>. For the documentation of the individual methods, see <xref:Microsoft.VisualStudio.TextTemplating.ITextTemplatingEngineHost>.
 
@@ -818,4 +818,4 @@ In this walkthrough, you created a text template transformation host that suppor
 
 ## See also
 
-- <xref:Microsoft.VisualStudio.TextTemplating.ITextTemplatingEngineHost>
+- <xref:Microsoft.VisualStudio.TextTemplating.ITextTemplatingEngineHost>