Merge pull request #3437 from gewarren/get-started

Move two quickstarts to get-started folder

Author: rjagiewich

.openpublishing.redirection.json

@@ -6941,6 +6941,16 @@
             "source_path": "docs/test/how-to-specify-plot-options-for-graphing-counters.md",
             "redirect_url": "/visualstudio/test/quickstart-create-a-load-test-project",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/ide/quickstart-editor.md",
+            "redirect_url": "/visualstudio/get-started/tutorial-editor",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/ide/quickstart-projects-solutions.md",
+            "redirect_url": "/visualstudio/get-started/tutorial-projects-solutions",
+            "redirect_document_id": false
         }
     ]
 }

docs/ide/media/quickstart-code-snippet-list.png renamed to docs/get-started/media/tutorial-code-snippet-list.png

@@ -2,8 +2,8 @@
 title: Introduction to editing
 ms.date: 11/30/2017
 ms.prod: visual-studio-dev15
-ms.technology: vs-ide-general
-ms.topic: quickstart
+ms.technology: vs-acquisition
+ms.topic: tutorial
 author: gewarren
 ms.author: gewarren
 manager: douge
@@ -30,7 +30,7 @@ Start by creating a new file and adding some code to it.
 
    A new file opens in the editor with the skeleton of a C# class. (Notice that we don't have to create a full Visual Studio project to gain some of the benefits that the code editor offers; all you need is a code file!)
 
-   ![C# code file in Visual Studio](media/quickstart-editor.png)
+   ![C# code file in Visual Studio](media/tutorial-editor.png)
 
 ## Use code snippets
 
@@ -40,23 +40,23 @@ Visual Studio provides useful *code snippets* that you can use to quickly and ea
 
    A pop-up dialog box appears with information about the `svm` code snippet.
 
-   ![IntelliSense for code snippet in Visual Studio](media/quickstart-intellisense-snippet.png)
+   ![IntelliSense for code snippet in Visual Studio](media/tutorial-intellisense-snippet.png)
 
 1. Press **Tab** twice to insert the code snippet.
 
    You see the `static void Main()` method signature get added to the file. The [Main()](/dotnet/csharp/programming-guide/main-and-command-args/) method is the entry point for C# applications.
 
 The available code snippets vary for different programming languages. You can look at the available code snippets for your language by choosing **Edit** > **IntelliSense** > **Insert Snippet**, and then choosing your language's folder. For C#, the list looks like this:
 
-![C# code snippet list](media/quickstart-code-snippet-list.png)
+![C# code snippet list](media/tutorial-code-snippet-list.png)
 
 The list includes snippets for creating a [class](/dotnet/csharp/programming-guide/classes-and-structs/classes), a [constructor](/dotnet/csharp/programming-guide/classes-and-structs/constructors), a [for](/dotnet/csharp/language-reference/keywords/for) loop, an [if](/dotnet/csharp/language-reference/keywords/if-else) or [switch](/dotnet/csharp/language-reference/keywords/switch) statement, and more.
 
 ## Comment out code
 
-The toolbar, which is the row of buttons under the menu bar in Visual Studio, can help make you more productive as you code. For example, you can toggle IntelliSense completion mode ([IntelliSense](using-intellisense.md) is a coding aid that displays a list of matching methods, amongst other things), increase or decrease a line indent, or comment out code that you don't want to compile. In this section, we'll comment out some code.
+The toolbar, which is the row of buttons under the menu bar in Visual Studio, can help make you more productive as you code. For example, you can toggle IntelliSense completion mode ([IntelliSense](../ide/using-intellisense.md) is a coding aid that displays a list of matching methods, amongst other things), increase or decrease a line indent, or comment out code that you don't want to compile. In this section, we'll comment out some code.
 
-![Editor toolbar](media/quickstart-editor-toolbar.png)
+![Editor toolbar](media/tutorial-editor-toolbar.png)
 
 1. Paste the following code into the `Main()` method body.
 
@@ -84,15 +84,15 @@ The toolbar, which is the row of buttons under the menu bar in Visual Studio, ca
 
 1. We're not using the `morewords` variable, but we may use it later so we don't want to completely delete it. Instead, let's comment out those lines. Select the entire definition of `morewords` to the closing semi-colon, and then choose the **Comment out the selected lines** button on the toolbar. If you prefer to use the keyboard, press **Ctrl**+**K**, **Ctrl**+**C**.
 
-   ![Comment out button](media/quickstart-comment-out.png)
+   ![Comment out button](media/tutorial-comment-out.png)
 
    The C# comment characters `//` are added to the beginning of each selected line to comment out the code.
 
 ## Collapse code blocks
 
 We don't want to see the empty [constructor](/dotnet/csharp/programming-guide/classes-and-structs/constructors) for `Class1` that was generated, so to unclutter our view of the code, let's collapse it. Choose the small gray box with the minus sign inside it in the margin of the first line of the constructor. Or, if you're a keyboard user, place the cursor anywhere in the constructor code and press **Ctrl**+**M**, **Ctrl**+**M**.
 
-![Outlining collapse button](media/quickstart-collapse.png)
+![Outlining collapse button](media/tutorial-collapse.png)
 
 The code block collapses to just the first line, followed by an ellipsis (`...`). To expand the code block again, click the same gray box that now has a plus sign in it, or press **Ctrl**+**M**, **Ctrl**+**M** again. This feature is called [Outlining](../ide/outlining.md) and is especially useful when you're collapsing long methods or entire classes.
 
@@ -104,7 +104,7 @@ The Visual Studio editor makes it easy to inspect the definition of a type, meth
 
    A pop-up window appears with the definition of the `String` class. You can scroll within the pop-up window, or even peek at the definition of another type from the peeked code.
 
-   ![Peek definition window](media/quickstart-peek-definition.png)
+   ![Peek definition window](media/tutorial-peek-definition.png)
 
 1. Close the peeked definition window by choosing the small box with an "x" at the top right of the pop-up window.
 
@@ -120,7 +120,7 @@ The Visual Studio editor makes it easy to inspect the definition of a type, meth
 
    You see IntelliSense show you **Quick Info** about the `query` symbol.
 
-   ![IntelliSense word completion in Visual Studio](media/quickstart-intellisense-completion-list.png)
+   ![IntelliSense word completion in Visual Studio](media/tutorial-intellisense-completion-list.png)
 
 1. To insert the rest of the word `query` by using IntelliSense's word completion functionality, press **Tab**.
 
@@ -143,7 +143,7 @@ Nobody gets code right the first time, and one of the things you might have to c
 
 1. Enter the desired name **words**. Notice that the reference to `words` in the query is also automatically renamed. Before you press **Enter**, select the **Include comments** checkbox in the **Rename** pop-up box.
 
-   ![Rename dialog box](media/quickstart-rename.png)
+   ![Rename dialog box](media/tutorial-rename.png)
 
 1. Press **Enter**.
 
@@ -152,7 +152,7 @@ Nobody gets code right the first time, and one of the things you might have to c
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Learn about projects and solutions](../ide/quickstart-projects-solutions.md)
+> [Learn about projects and solutions](../get-started/tutorial-projects-solutions.md)
 
 ## See also
 

docs/ide/media/quickstart-collapse.png renamed to docs/get-started/media/tutorial-collapse.png

@@ -2,8 +2,8 @@
 title: Introduction to projects and solutions
 ms.date: 12/11/2017
 ms.prod: visual-studio-dev15
-ms.technology: vs-ide-general
-ms.topic: quickstart
+ms.technology: vs-acquisition
+ms.topic: tutorial
 author: gewarren
 ms.author: gewarren
 manager: douge
@@ -37,7 +37,7 @@ We'll start our exploration by creating an empty solution. After you get to know
 
 1. In the left pane, expand **Other Project Types**, then choose **Visual Studio Solutions**. In the center pane, choose the **Blank Solution** template. Name your solution **QuickSolution**, then choose the **OK** button.
 
-   ![Blank solution template in Visual Studio](media/quickstart-projects-new-solution.png)
+   ![Blank solution template in Visual Studio](media/tutorial-projects-new-solution.png)
 
    The **Start Page** closes, and a solution appears in **Solution Explorer** on the right-hand side of the Visual Studio window. You'll probably use **Solution Explorer** often, to browse the contents of your projects.
 
@@ -56,7 +56,7 @@ Now let's add our first project to the solution. We'll start with an empty proje
    > [!NOTE]
    > If you don't see **Visual C#** in the left pane of the dialog box, you need to install the **.NET desktop development** Visual Studio *workload*. Visual Studio uses workload-based installation to only install the components you need for the type of development you do. An easy way to install a new workload is to choose the **Open Visual Studio Installer** link in the bottom left corner of the **Add New Project** dialog box. After Visual Studio Installer launches, choose the **.NET desktop development** workload and then the **Modify** button.
 
-   ![Open Visual Studio Installer link](media/quickstart-projects-open-installer.png)
+   ![Open Visual Studio Installer link](media/tutorial-projects-open-installer.png)
 
 ## Add an item to the project
 
@@ -110,15 +110,15 @@ Let's add a unit test project to our solution. This time we'll start from a proj
 
    A second project is added to **Solution Explorer**, and a file named *UnitTest1.vb* opens in the editor. *.vb* is the file extension that is given to Visual Basic code files.
 
-   ![Visual Studio Solution Explorer with two projects](media/quickstart-projects-solution-explorer.png)
+   ![Visual Studio Solution Explorer with two projects](media/tutorial-projects-solution-explorer.png)
 
 ## Add a project reference
 
 We're going to use the new unit test project to test our method in the **QuickDate** project, so we need to add a reference to that project. This creates a *build dependency* between the two projects, meaning that when you build the solution, **QuickDate** is built before **QuickTest**.
 
 1. Choose the **References** node in the **QuickTest** project, and from the right-click or context menu, choose **Add Reference**.
 
-   ![Add Reference menu](media/quickstart-projects-add-reference.png)
+   ![Add Reference menu](media/tutorial-projects-add-reference.png)
 
    The **Reference Manager** dialog box opens.
 
@@ -152,7 +152,7 @@ We're going to use the new unit test project to test our method in the **QuickDa
 
    The code file should look like this:
 
-   ![CSharp code](media/quickstart-projects-cs-code.png)
+   ![CSharp code](media/tutorial-projects-cs-code.png)
 
 ## Project properties
 
@@ -162,15 +162,15 @@ The line in the *Calendar.cs* file that contains the <xref:System.Runtime.Compil
 
    The *property pages* for the project open on the **Application** tab. The property pages contain various settings for the project. Notice that the assembly name of the **QuickTest** project is indeed "QuickTest". If you wanted to change it, this is where you'd do that. Then, when you build the test project, the name of the resulting binary file would change from *QuickTest.dll* to whatever you chose.
 
-   ![Project properties](media/quickstart-projects-properties.png)
+   ![Project properties](media/tutorial-projects-properties.png)
 
 1. Explore some of the other tabs of the project's property pages, such as **Compile** and **Settings**. These tabs are different for different types of projects.
 
 ## Next steps
 
 If you want to check that your unit test is working, choose **Test** > **Run** > **All Tests** from the menu bar. A window called **Test Explorer** opens, and you should see that the **TestGetCurrentDate** test passes.
 
-![Test Explorer in Visual Studio showing passed test](media/quickstart-projects-test-explorer.png)
+![Test Explorer in Visual Studio showing passed test](media/tutorial-projects-test-explorer.png)
 
 > [!TIP]
 > If **Test Explorer** doesn't open automatically, open it by choosing **Test** > **Windows** > **Test Explorer** from the menu bar.

docs/ide/media/quickstart-comment-out.png renamed to docs/get-started/media/tutorial-comment-out.png

@@ -95,7 +95,7 @@ Tutorials, videos, and other documentation show you ways to create code and apps
         </a>
     </li>
     <li>
-        <a href="/visualstudio/ide/quickstart-projects-solutions">
+        <a href="/visualstudio/get-started/tutorial-projects-solutions">
         <div class="cardSize">
             <div class="cardPadding">
                 <div class="card">
@@ -113,7 +113,7 @@ Tutorials, videos, and other documentation show you ways to create code and apps
         </a>
     </li>
     <li>
-        <a href="/visualstudio/ide/quickstart-editor">
+        <a href="/visualstudio/get-started/tutorial-editor">
         <div class="cardSize">
             <div class="cardPadding">
                 <div class="card">

docs/ide/media/quickstart-editor-toolbar.png renamed to docs/get-started/media/tutorial-editor-toolbar.png

@@ -101,10 +101,10 @@ Should you encounter any problems while you're using Visual Studio, or if you ha
 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](../ide/quickstart-editor.md)
+> [Learn about the code editor](../get-started/tutorial-editor.md)
 
 > [!div class="nextstepaction"]
-> [Learn about projects and solutions](../ide/quickstart-projects-solutions.md)
+> [Learn about projects and solutions](../get-started/tutorial-projects-solutions.md)
 
 ## See also
 

docs/ide/media/quickstart-editor.png renamed to docs/get-started/media/tutorial-editor.png

@@ -101,10 +101,10 @@ Should you encounter any problems while you're using Visual Studio, or if you ha
 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](../ide/quickstart-editor.md)
+> [Learn about the code editor](../get-started/tutorial-editor.md)
 
 > [!div class="nextstepaction"]
-> [Learn about projects and solutions](../ide/quickstart-projects-solutions.md)
+> [Learn about projects and solutions](../get-started/tutorial-projects-solutions.md)
 
 ## See also
 

docs/ide/media/quickstart-intellisense-completion-list.png renamed to docs/get-started/media/tutorial-intellisense-completion-list.png

@@ -22,7 +22,7 @@ The Visual Studio *integrated development environment* is a creative launching p
 
 This image shows Visual Studio with an open project and several key tool windows you'll likely use:
 
-- [**Solution Explorer**](../ide/solutions-and-projects-in-visual-studio.md) (top right) lets you view, navigate, and manage your code files. **Solution Explorer** can help organize your code by grouping the files into [solutions and projects](quickstart-projects-solutions.md).
+- [**Solution Explorer**](../ide/solutions-and-projects-in-visual-studio.md) (top right) lets you view, navigate, and manage your code files. **Solution Explorer** can help organize your code by grouping the files into [solutions and projects](../get-started/tutorial-projects-solutions.md).
 
 - The [editor window](../ide/writing-code-in-the-code-and-text-editor.md) (center), where you'll likely spend a majority of your time, displays file contents. This is where you can edit code or design a user interface such as a window with buttons and text boxes.
 
@@ -258,9 +258,9 @@ To learn about other ways you can personalize the IDE, see [Personalize Visual S
 
 Explore Visual Studio further by following along with one of these introductory articles:
 
-- Get acquainted with the code editor in [Learn to use the code editor](quickstart-editor.md)
+- Get acquainted with the code editor in [Learn to use the code editor](../get-started/tutorial-editor.md)
 
-- Learn how Visual Studio organizes code in [Learn about projects and solutions](quickstart-projects-solutions.md)
+- Learn how Visual Studio organizes code in [Learn about projects and solutions](../get-started/tutorial-projects-solutions.md)
 
 If you're ready to dive into more coding, one of the following language-specific quickstarts is a good next step:
 

docs/ide/media/quickstart-intellisense-snippet.png renamed to docs/get-started/media/tutorial-intellisense-snippet.png

@@ -6,9 +6,9 @@
     - name: About Visual Studio 2017
       href: ide/visual-studio-ide.md
     - name: About the code editor
-      href: ide/quickstart-editor.md
+      href: get-started/tutorial-editor.md
     - name: About projects and solutions
-      href: ide/quickstart-projects-solutions.md
+      href: get-started/tutorial-projects-solutions.md
     - name: More Visual Studio features
       href: ide/advanced-feature-overview.md
 - name: Installation