Skip to content

Commit bd8b7b8

Browse files
committed
Merged main into live
2 parents c51c04c + b73cb26 commit bd8b7b8

6 files changed

+18
-8
lines changed

docs/debugger/diagnostic-messages-in-the-output-window.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Send messages to the Output window
33
description: Write run-time messages to the Output window in Visual Studio using the Debug class or the Trace class, which are part of the System.Diagnostics class library.
4-
ms.date: 11/08/2018
4+
ms.date: 10/03/2024
55
ms.topic: how-to
66
helpviewer_keywords:
77
- diagnostic messages [C#]
@@ -28,7 +28,7 @@ You can write run-time messages to the **Output** window using the <xref:System.
2828
## Output methods
2929
The <xref:System.Diagnostics.Trace> and <xref:System.Diagnostics.Debug> classes provide the following output methods:
3030

31-
- Various `Write` methods, which output information without breaking execution. These methods replace the `Debug.Print` method used in previous versions of Visual Basic.
31+
- Various [Write](/dotnet/api/system.diagnostics.debug#methods) methods, which output information without breaking execution. These methods replace the `Debug.Print` method used in previous versions of Visual Basic.
3232

3333
- <xref:System.Diagnostics.Debug.Assert%2A?displayProperty=fullName> and <xref:System.Diagnostics.Trace.Assert%2A?displayProperty=fullName> methods, which break execution and output information if a specified condition fails. By default, the `Assert` method displays the information in a dialog box. For more information, see [Assertions in managed code](../debugger/assertions-in-managed-code.md).
3434

docs/ide/code-styles-and-code-cleanup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Code style options and code cleanup
33
description: Learn how to configure Visual Studio to apply code style preferences using the Code Cleanup (Visual Studio 2019) and Format Document (Visual Studio 2017) commands.
4-
ms.date: 07/19/2024
4+
ms.date: 10/03/2024
55
ms.topic: conceptual
66
author: mikejo5000
77
ms.author: mikejo
@@ -120,7 +120,7 @@ Most of the code cleanup settings map to one or more .NET code styles supported
120120
|Remove unnecessary Imports or usings|[IDE0005](/dotnet/fundamentals/code-analysis/style-rules/ide0005)|
121121
|Sort imports or usings|[dotnet_sort_system_directives_first](/dotnet/fundamentals/code-analysis/style-rules/dotnet-formatting-options#dotnet_sort_system_directives_first)</br>[dotnet_separate_import_directive_groups](/dotnet/fundamentals/code-analysis/style-rules/dotnet-formatting-options#dotnet_separate_import_directive_groups)|
122122
|Apply file header preferences|[file_header_template](/dotnet/fundamentals/code-analysis/style-rules/ide0073#file_header_template)|
123-
|Remove unused variables|[IDE0051](/dotnet/fundamentals/code-analysis/style-rules/ide0051)|
123+
|Remove unused variables|[CS0219](/dotnet/csharp/misc/cs0219)|
124124
|Apply object creation preferences|[visual_basic_style_prefer_simplified_object_creation](/dotnet/fundamentals/code-analysis/style-rules/ide0140#visual_basic_style_prefer_simplified_object_creation)|
125125
|Apply IsNot preferences|[visual_basic_style_prefer_isnot_expression](/dotnet/fundamentals/code-analysis/style-rules/ide0084#visual_basic_style_prefer_isnot_expression)|
126126
|Add 'this' or 'Me' qualification|[IDE0003-IDE0009](/dotnet/fundamentals/code-analysis/style-rules/ide0003-ide0009)|

docs/ide/creating-solutions-and-projects.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Create projects & solutions"
33
description: Create Visual Studio solutions and projects and use them to store artifacts, including source code files, bitmaps, icons, and component and service references.
4-
ms.date: 08/19/2024
4+
ms.date: 10/03/2024
55
ms.topic: how-to
66
f1_keywords:
77
- vs.openprojectfromweb
@@ -100,6 +100,12 @@ After you create an empty solution, you can add new or existing projects or item
100100

101101
As noted earlier, you can also open code files without using a project or solution. To learn about developing code in this way, see [Develop code in Visual Studio without projects or solutions](../ide/develop-code-in-visual-studio-without-projects-or-solutions.md).
102102

103+
## Multi-project solution
104+
105+
You can create a solution that contains multiple projects. Start with an [empty solution](#create-empty-solutions) or a [solution containing a project](#create-a-project-by-using-a-project-template) and add multiple new or existing projects to it by using **Add** > **New project**/**Existing project**. For example, you can create a solution that contains a C# project and a Visual Basic project.
106+
107+
To learn more about building a solution that contains multiple projects, see [Create and remove project dependencies](how-to-create-and-remove-project-dependencies.md) and [Set multiple startup projects](how-to-set-multiple-startup-projects.md).
108+
103109
## Delete a solution, project, or item
104110

105111
You can use the right-click context menu to delete or remove solutions, projects, or items in Visual Studio, but that only removes them from the current solution or project.
@@ -124,3 +130,4 @@ You can access File Explorer in Windows by using Solution Explorer in Visual Stu
124130
- [Introduction to projects and solutions](../get-started/tutorial-projects-solutions.md)
125131
- [Manage project and solution properties](managing-project-and-solution-properties.md)
126132
- [Filtered solutions in Visual Studio](filtered-solutions.md)
133+
- [Build and clean projects and solutions](building-and-cleaning-projects-and-solutions-in-visual-studio.md)

docs/ide/default-keyboard-shortcuts-in-visual-studio.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ For a list of common keyboard shortcuts and other productivity information, see:
2525

2626
For more information about accessibility in Visual Studio, see [Accessibility tips and tricks](../ide/reference/accessibility-tips-and-tricks.md) and [How to: Use the keyboard exclusively](../ide/reference/how-to-use-the-keyboard-exclusively.md).
2727

28-
The keyboard shortcuts in Visual Studio may vary depending on your keyboard layout and language settings. You can [identify the keyboard shortcut for a command](identifying-and-customizing-keyboard-shortcuts-in-visual-studio.md#identify-a-keyboard-shortcut) or [customize your keyboard shortcut](identifying-and-customizing-keyboard-shortcuts-in-visual-studio.md#customize-a-keyboard-shortcut). See the [Dev Community ticket](https://developercommunity.visualstudio.com/t/Copying-a-specific-cell-for-an-error-in/424849?q=error+copy&ftype=idea&stateGroup=active) related to this issue for more information.
28+
The keyboard shortcuts in Visual Studio may vary depending on your keyboard layout and language settings. You can [identify the keyboard shortcut for a command](identifying-and-customizing-keyboard-shortcuts-in-visual-studio.md#identify-a-keyboard-shortcut) or [customize your keyboard shortcut](identifying-and-customizing-keyboard-shortcuts-in-visual-studio.md#customize-a-keyboard-shortcut). See the [Dev Community ticket](https://developercommunity.visualstudio.com/t/Issue-with-New-Ctrl---Comment-Shortc/10725157?q=keyboard+language&ftype=idea&stateGroup=active) related to this issue for more information.
2929

3030
## Printable shortcut cheatsheet
3131

docs/ide/how-to-manage-editor-modes.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Full screen and virtual space mode
33
description: Learn how to manage the Visual Studio editor modes to display all of the tools and windows in a way that works best for you.
4-
ms.date: 02/06/2023
4+
ms.date: 10/03/2024
55
ms.topic: how-to
66
helpviewer_keywords:
77
- word wrap
@@ -31,6 +31,8 @@ With Visual Studio, you can view the code editor in various display modes.
3131
> [!NOTE]
3232
> The dialog boxes and menu commands you see might differ from those described in this article depending on your active settings or edition. To change your settings, for example to **General** or **Visual C++** settings, select **Tools** > **Import and Export Settings**, and then select **Reset all settings**.
3333
34+
The keyboard shortcuts in Visual Studio may vary depending on your keyboard layout and language settings. You can [identify the keyboard shortcut for a command](identifying-and-customizing-keyboard-shortcuts-in-visual-studio.md#identify-a-keyboard-shortcut) or [customize your keyboard shortcut](identifying-and-customizing-keyboard-shortcuts-in-visual-studio.md#customize-a-keyboard-shortcut). See the [Dev Community ticket](https://developercommunity.visualstudio.com/t/Issue-with-New-Ctrl---Comment-Shortc/10725157?q=keyboard+language&ftype=idea&stateGroup=active) related to this issue for more information.
35+
3436
## Enable full screen mode
3537

3638
You can choose to hide all tool windows and view only document windows by enabling **Full Screen** mode.

docs/version-control/git-line-staging.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,6 @@ ms.topic: concept-article
77
author: ghogen
88
ms.author: ghogen
99
ms.manager: mijacobs
10-
1110
ms.subservice: general-ide
1211
monikerRange: vs-2022
1312

@@ -78,6 +77,8 @@ You can stage any chunk of code by using the Peek Difference UI. Hover over the
7877
>
7978
> :::image type="content" source="media/vs-2022/git-stage-change-difference.png" border="false" alt-text="Screenshot of the Stage Change difference view in Visual Studio 2022." lightbox="media/vs-2022/git-stage-change-difference.png":::
8079
80+
You can enable or disable the staging controls in the difference view by clicking the **Show staging controls** button.
81+
8182
## Commit staged changes
8283

8384
After you prepare your commit by reviewing and staging the desired changes, you can create your commit by using the **Git Changes** window. Enter a commit message and select **Commit Staged** to complete the process:

0 commit comments

Comments
 (0)