|
1 | 1 | ---
|
2 | 2 | title: Introduction to projects and solutions
|
3 | 3 | description: Learn about the difference between projects and solutions and how to use them in Visual Studio.
|
4 |
| -ms.date: 11/12/2021 |
| 4 | +ms.date: 11/22/2022 |
5 | 5 | ms.technology: vs-ide-general
|
6 | 6 | ms.custom: [vs-acquisition, get-started, SEO-VS-2020]
|
7 | 7 | ms.topic: tutorial
|
@@ -42,7 +42,7 @@ In Visual Studio, a solution isn't an "answer". A solution is simply a container
|
42 | 42 |
|
43 | 43 | ### Create a solution
|
44 | 44 |
|
45 |
| -Start your exploration by creating an empty solution. After you get to know Visual Studio, you probably won't create empty solutions very often. When you create a new project, Visual Studio automatically creates a solution for the project unless a solution is already open. |
| 45 | +Start your exploration by creating an empty solution. After you get to know Visual Studio, you probably won't create empty solutions often. When you create a new project, Visual Studio automatically creates a solution for the project unless a solution is already open. |
46 | 46 |
|
47 | 47 | ::: moniker range="vs-2019"
|
48 | 48 |
|
@@ -124,7 +124,7 @@ Now add your first project to the solution. Start with an empty project, and add
|
124 | 124 |
|
125 | 125 | 1. On the **Configure your new project** page, name the project **QuickDate**, and then select **Create**.
|
126 | 126 |
|
127 |
| - The **QuickDate** project appears under the solution in **Solution Explorer**. Currently the project contains a single file called **App.config**. |
| 127 | + The **QuickDate** project appears under the solution in **Solution Explorer**. The project contains a References node and a single file named **App.config**. |
128 | 128 |
|
129 | 129 | ::: moniker-end
|
130 | 130 |
|
@@ -231,7 +231,7 @@ You'll use the new unit test project to test your method in the **QuickDate** pr
|
231 | 231 |
|
232 | 232 | 1. In **Solution Explorer**, right-click the **References** node of the **QuickTest** project, and select **Add Reference** from the context menu.
|
233 | 233 |
|
234 |
| -1. In the **Reference Manager** dialog box, under **Projects**, select the checkbox next to **QuickDate**, and then select **OK**. |
| 234 | +1. In the **Reference Manager** dialog box, select **Projects**. In the middle pane, select the checkbox next to **QuickDate**, and then select **OK**. |
235 | 235 |
|
236 | 236 | A reference to the **QuickDate** project appears under the **QuickTest** project in **Solution Explorer**.
|
237 | 237 |
|
@@ -263,7 +263,7 @@ You'll use the new unit test project to test your method in the **QuickDate** pr
|
263 | 263 |
|
264 | 264 | A red squiggle appears under some of the code. You can fix this error by making the test project a [friend assembly](/dotnet/standard/assembly/friend-assemblies) to the **QuickDate** project.
|
265 | 265 |
|
266 |
| -1. In the *Calendar.cs* file, add the following [using statement](/dotnet/csharp/language-reference/keywords/using-statement) and <xref:System.Runtime.CompilerServices.InternalsVisibleToAttribute> attribute to the top of the file to resolve the error in the test project. |
| 266 | +1. In the ***Calendar.cs*** file, add the following [using statement](/dotnet/csharp/language-reference/keywords/using-statement) and <xref:System.Runtime.CompilerServices.InternalsVisibleToAttribute> attribute to the top of the file to resolve the error in the test project. |
267 | 267 |
|
268 | 268 | ```csharp
|
269 | 269 | using System.Runtime.CompilerServices;
|
@@ -302,7 +302,7 @@ To check that your unit test is working, choose **Test** > **Run All Tests** fro
|
302 | 302 | ::: moniker-end
|
303 | 303 |
|
304 | 304 | > [!TIP]
|
305 |
| -> If **Test Explorer** doesn't open automatically, open it by choosing **Test** > **Test Explorer** from the menu bar. |
| 305 | +> You can also open **Test Explorer** by choosing **Test** > **Test Explorer** from the menu bar. |
306 | 306 |
|
307 | 307 | ## Project properties
|
308 | 308 |
|
@@ -331,7 +331,6 @@ The line in the *Calendar.cs* file that contains the <xref:System.Runtime.Compil
|
331 | 331 | ## See also
|
332 | 332 |
|
333 | 333 | - [Work with projects and solutions](../ide/creating-solutions-and-projects.md)
|
| 334 | +- [Develop code in Visual Studio without projects or solutions](../ide/develop-code-in-visual-studio-without-projects-or-solutions.md) |
334 | 335 | - [Manage project and solution properties](../ide/managing-project-and-solution-properties.md)
|
335 | 336 | - [Manage references in a project](../ide/managing-references-in-a-project.md)
|
336 |
| -- [Develop code in Visual Studio without projects or solutions](../ide/develop-code-in-visual-studio-without-projects-or-solutions.md) |
337 |
| -- [Visual Studio IDE overview](../get-started/visual-studio-ide.md) |
0 commit comments