You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
17
+
18
+
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=button+cta&utm_content=download+vs2017) page to install it for free.
19
+
20
+
## Start Page
21
+
22
+
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 project or code folder. On the right is a feed of the latest developer news.
23
+
24
+
25
+
26
+
If you close the **Start Page** and want to see it again, you can reopen it from the **File** menu.
27
+
28
+
29
+
30
+
To continue exploring the IDE, let's create a new project.
31
+
32
+
1. On the **Start Page**, in the search box under **New project**, enter **console** to filter the list of project types. Choose either a C# or VB **Console App (.NET Framework)**. (Alternatively, if you are a C++, Javascript, or other language developer, feel free to create a project in one of those languages. The UI we'll be looking at is similar for all languages.)
33
+
34
+
1. In the **New Project** dialog box, accept the default project name and choose **OK**.
35
+
36
+
The project is created and a file named *Program.cs* or *Program.vb* 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.
37
+
38
+
## Solution Explorer
39
+
40
+
**Solution Explorer** 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**.
41
+
42
+
43
+
44
+
## Menus
45
+
46
+
The menu bar along the top of the IDE 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 the IDE by selecting **Options**, or add features to your installation by selecting **Get Tools and Features**.
47
+
48
+
49
+
50
+
Let's open the **Error List** window by choosing the **View** menu, and then **Error List**.
51
+
52
+
## Error List
53
+
54
+
The **Error List** shows you errors, warning, and messages regarding the current state of your code. If there were any errors (such as a syntax typo) in your file, or anywhere in your project, they would be listed here.
55
+
56
+
57
+
58
+
## Output window
59
+
60
+
The **Output** window shows you output messages from Build and Source Control.
61
+
62
+
Let's build the project to see some output logging. From the **Build** menu, choose **Build Solution**. The **Output** window automatically obtains focus and display a successful build message.
63
+
64
+
65
+
66
+
## Quick Launch
67
+
68
+
The **Quick Launch** box is a quick and easy way to do pretty much anything in the IDE. 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, let's say we want to increase the build output's verbosity to display additional logging information about what exactly build is doing:
69
+
70
+
1. Enter **verbosity** into the **Quick Launch** box, and then choose **Projects and Solutions --> Build and Run** under the **Options** category.
71
+
72
+
73
+
74
+
The **Options** dialog box opens to the **Build and Run** options page.
75
+
76
+
1. Under **MSBuild project build output verbosity**, choose **Normal**, and then click **OK**.
77
+
78
+
1. Now we'll build the project again by right-clicking on the **ConsoleApp1** project in **Solution Explorer**, and choosing **Rebuild** from the context menu.
79
+
80
+
This time the **Output** window shows more verbose logging from the build process, including which files were copied where.
81
+
82
+
## Send Feedback menu
83
+
84
+
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 IDE, next to the **Quick Launch** box.
85
+
86
+
87
+
88
+
## Next steps
89
+
90
+
We've looked at just a few of the features of the Visual Studio IDE to get acquainted with the user interface. To explore further:
91
+
92
+
- Browse the **General User Interface Elements** section of the VS documentation, which goes into more depth about windows such as the [Error List](../ide/reference/error-list-window.md), [Output window](../ide/reference/output-window.md), [Properties window](../ide/reference/properties-window.md), and [Options dialog box](../ide/reference/options-dialog-box-visual-studio.md)
93
+
94
+
- Take a more in-depth tour of the IDE, and even dabble in debugging, in [Overview of the Visual Studio IDE](../ide/visual-studio-ide.md)
95
+
96
+
## See also
97
+
98
+
-[Quickstart: Personalize the IDE](../ide/personalizing-the-visual-studio-ide.md)
99
+
-[Quickstart: Write code in the editor](../ide/quickstart-editor.md)
100
+
-[Quickstart: Projects and solutions](../ide/quickstart-projects-solutions.md)
Copy file name to clipboardExpand all lines: docs/ide/quickstart-ide-orientation.md
+14-12Lines changed: 14 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Tour of the Visual Studio IDE
3
-
ms.date: 11/15/2017
3
+
ms.date: 07/12/2018
4
4
ms.prod: visual-studio-dev15
5
5
ms.technology: vs-ide-general
6
6
ms.topic: quickstart
@@ -9,6 +9,8 @@ ms.author: gewarren
9
9
manager: douge
10
10
ms.workload:
11
11
- "multiple"
12
+
experimental: true
13
+
experiment_id: 92a235b7-7520-4b
12
14
---
13
15
# Quickstart: First look at the Visual Studio IDE
14
16
@@ -20,15 +22,15 @@ If you haven't already installed Visual Studio, go to the [Visual Studio downloa
20
22
21
23
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 project or code folder. On the right is a feed of the latest developer news.
28
30
29
31
To continue exploring the IDE, let's create a new project.
30
32
31
-
1. On the **Start Page**, in the search box under **New project**, enter `console` to filter the list of project types. Choose either a C# or VB **Console App (.NET Framework)**. (Alternatively, if you are a C++, Javascript, or other language developer, feel free to create a project in one of those languages. The UI we'll be looking at is similar for all languages.)
33
+
1. On the **Start Page**, in the search box under **New project**, enter **console** to filter the list of project types. Choose either a C# or VB **Console App (.NET Framework)**. (Alternatively, if you are a C++, Javascript, or other language developer, feel free to create a project in one of those languages. The UI we'll be looking at is similar for all languages.)
32
34
33
35
1. In the **New Project** dialog box, accept the default project name and choose **OK**.
34
36
@@ -38,37 +40,37 @@ To continue exploring the IDE, let's create a new project.
38
40
39
41
**Solution Explorer** 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**.
42
44
43
45
## Menus
44
46
45
47
The menu bar along the top of the IDE 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 the IDE by selecting **Options**, or add features to your installation by selecting **Get Tools and Features**.
46
48
47
-
49
+
48
50
49
51
Let's open the **Error List** window by choosing the **View** menu, and then **Error List**.
50
52
51
53
## Error List
52
54
53
55
The **Error List** shows you errors, warning, and messages regarding the current state of your code. If there were any errors (such as a syntax typo) in your file, or anywhere in your project, they would be listed here.
56
58
57
59
## Output window
58
60
59
61
The **Output** window shows you output messages from Build and Source Control.
60
62
61
63
Let's build the project to see some output logging. From the **Build** menu, choose **Build Solution**. The **Output** window automatically obtains focus and display a successful build message.
62
64
63
-
65
+
64
66
65
67
## Quick Launch
66
68
67
69
The **Quick Launch** box is a quick and easy way to do pretty much anything in the IDE. 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, let's say we want to increase the build output's verbosity to display additional logging information about what exactly build is doing:
68
70
69
-
1. Enter `verbosity` into the **Quick Launch** box, and then choose **Projects and Solutions --> Build and Run** under the **Options** category.
71
+
1. Enter **verbosity** into the **Quick Launch** box, and then choose **Projects and Solutions --> Build and Run** under the **Options** category.
72
74
73
75
The **Options** dialog box opens to the **Build and Run** options page.
74
76
@@ -82,7 +84,7 @@ The **Quick Launch** box is a quick and easy way to do pretty much anything in t
82
84
83
85
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 IDE, next to the **Quick Launch** box.
If the images don't include a Visual Studio feature that you require, provide feedback through the feedback tool in the upper-right corner of the page.
Copy file name to clipboardExpand all lines: docs/test/configure-unit-tests-by-using-a-dot-runsettings-file.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Run settings files are optional. If you don't require any special configuration,
18
18
19
19
## Specify a run settings file
20
20
21
-
Run settings files can be used to configure tests that are run from the command line, in the IDE, or in a [build workflow](/vsts/pipelines/test/getting-started-with-continuous-testing?view=vsts) using Visual Studio Team Services (VSTS) or Team Foundation Server (TFS).
21
+
Run settings files can be used to configure tests that are run from the [command line](vstest-console-options.md), in the IDE, or in a [build workflow](/vsts/pipelines/test/getting-started-with-continuous-testing?view=vsts) using Visual Studio Team Services (VSTS) or Team Foundation Server (TFS).
22
22
23
23
### Specify a run settings file in the IDE
24
24
@@ -40,6 +40,8 @@ To run tests from the command line, use *vstest.console.exe* and specify the set
Copy file name to clipboardExpand all lines: docs/test/how-to-select-the-active-run-setting-for-a-load-test.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ If your load test contains only one run setting node under the **Run Settings**
24
24
25
25
In the Load Test Editor, the active run setting is identified by the "[Active]" suffix.
26
26
27
-
## Selecting the Active Run Setting
27
+
## Select the Active Run Setting
28
28
29
29
### To select the active run setting in a load test
30
30
@@ -41,15 +41,15 @@ In the Load Test Editor, the active run setting is identified by the "[Active]"
41
41
> [!NOTE]
42
42
> You can override the active run setting by setting an environment variable named `Test.UseRunSetting=<run setting name>`. This is useful when you run a load test from the command line or from a batch file. This lets you choose different run settings without opening your load test.
43
43
44
+
## Specify the Run Setting to Use from the Command Line
44
45
45
-
## Specifying the Run Setting to Use from the Command Line
46
-
You can override the default run settings in your load test by setting an environment variable from the command line:
46
+
You can override the default run settings in your load test by setting an environment variable from the command line:
0 commit comments