Skip to content

Commit 4333131

Browse files
learn-build-service-prod[bot]learn-build-service-prod[bot]
authored
Merge pull request #14666 from MicrosoftDocs/main
Auto Publish – main to live - 2025-11-20 23:00 UTC
2 parents 4f4bf5d + bf0078b commit 4333131

5 files changed

Lines changed: 83 additions & 122 deletions

File tree

‎docs/extensibility/migration/modernize-theme-colors.md‎

Lines changed: 2 additions & 92 deletions
Original file line numberDiff line numberDiff line change
@@ -103,98 +103,6 @@ You can make a previous theme compatible with Visual Studio 2026 by merging its
103103

104104
2. Append the below set of tokens as the last two categories after the previous theme tokens. Make sure the category name and GUID are copied exactly as below.
105105

106-
Minimal migration token overrides for a Light based theme:
107-
108-
```xml
109-
<Category Name="Shell" GUID="{73708ded-2d56-4aad-b8eb-73b20d3f4bff}">
110-
<Color Name="AccentFillDefault">
111-
<Background Type="CT_RAW" Source="FF5649B0" />
112-
</Color>
113-
<Color Name="AccentFillSecondary">
114-
<Background Type="CT_RAW" Source="E55649B0" />
115-
</Color>
116-
<Color Name="AccentFillTertiary">
117-
<Background Type="CT_RAW" Source="CC5649B0" />
118-
</Color>
119-
<Color Name="SolidBackgroundFillTertiary">
120-
<Background Type="CT_RAW" Source="FFF9F9F9" />
121-
</Color>
122-
<Color Name="SolidBackgroundFillQuaternary">
123-
<Background Type="CT_RAW" Source="FFFFFFFF" />
124-
</Color>
125-
<Color Name="SurfaceBackgroundFillDefault">
126-
<Background Type="CT_RAW" Source="FFF9F9F9" />
127-
</Color>
128-
<Color Name="TextFillSecondary">
129-
<Background Type="CT_RAW" Source="9E000000" />
130-
</Color>
131-
</Category>
132-
<Category Name="ShellInternal" GUID="{5af241b7-5627-4d12-bfb1-2b67d11127d7}">
133-
<Color Name="EnvironmentBackground">
134-
<Background Type="CT_RAW" Source="FFEEEEEE" />
135-
</Color>
136-
<Color Name="EnvironmentBorder">
137-
<Background Type="CT_RAW" Source="FF5649B0" />
138-
</Color>
139-
<Color Name="EnvironmentIndicator">
140-
<Background Type="CT_RAW" Source="66757575" />
141-
</Color>
142-
<Color Name="EnvironmentLogo">
143-
<Background Type="CT_RAW" Source="FF5649B0" />
144-
</Color>
145-
<Color Name="EnvironmentLayeredBackground">
146-
<Background Type="CT_RAW" Source="80FFFFFF" />
147-
</Color>
148-
</Category>
149-
```
150-
151-
Minimal migration token overrides for a Dark based theme:
152-
153-
```xml
154-
<Category Name="Shell" GUID="{73708ded-2d56-4aad-b8eb-73b20d3f4bff}">
155-
<Color Name="AccentFillDefault">
156-
<Background Type="CT_RAW" Source="FF9184EE" />
157-
</Color>
158-
<Color Name="AccentFillSecondary">
159-
<Background Type="CT_RAW" Source="80000000" />
160-
</Color>
161-
<Color Name="AccentFillTertiary">
162-
<Background Type="CT_RAW" Source="CC9184EE" />
163-
</Color>
164-
<Color Name="SolidBackgroundFillTertiary">
165-
<Background Type="CT_RAW" Source="FF282828" />
166-
</Color>
167-
<Color Name="SolidBackgroundFillQuaternary">
168-
<Background Type="CT_RAW" Source="FF2C2C2C" />
169-
</Color>
170-
<Color Name="SurfaceBackgroundFillDefault">
171-
<Background Type="CT_RAW" Source="FF2C2C2C" />
172-
</Color>
173-
<Color Name="TextFillSecondary">
174-
<Background Type="CT_RAW" Source="C8FFFFFF" />
175-
</Color>
176-
</Category>
177-
<Category Name="ShellInternal" GUID="{5af241b7-5627-4d12-bfb1-2b67d11127d7}">
178-
<Color Name="EnvironmentBackground">
179-
<Background Type="CT_RAW" Source="FF1C1C1C" />
180-
</Color>
181-
<Color Name="EnvironmentBorder">
182-
<Background Type="CT_RAW" Source="FF9184EE" />
183-
</Color>
184-
<Color Name="EnvironmentIndicator">
185-
<Background Type="CT_RAW" Source="66757575" />
186-
</Color>
187-
<Color Name="EnvironmentLogo">
188-
<Background Type="CT_RAW" Source="FF9184EE" />
189-
</Color>
190-
<Color Name="EnvironmentLayeredBackground">
191-
<Background Type="CT_RAW" Source="4D3A3A3A" />
192-
</Color>
193-
</Category>
194-
```
195-
196-
3. Adjust the color values to fit the previous theme as needed.
197-
198106
### Minimal token set starter for a light-based theme
199107

200108
<!-- Minimal compatibility section to append to an existing light based .vstheme -->
@@ -295,6 +203,8 @@ Minimal migration token overrides for a Dark based theme:
295203
</Theme>
296204
```
297205

206+
3. Adjust the color values to fit the previous theme as needed.
207+
298208
## FAQ
299209

300210
### Why was this a breaking change?

‎docs/ide/how-to-save-and-open-files-with-encoding.md‎

Lines changed: 25 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Save and open files with encoding
33
description: Learn how to save and open files with specific encoding in Visual Studio, and ensure files open correctly in subsequent use.
4-
ms.date: 01/13/2025
4+
ms.date: 11/13/2025
55
ms.topic: how-to
66
helpviewer_keywords:
77
- Unicode, bidirectional language support
@@ -47,12 +47,34 @@ Follow these steps to save your file with encoding:
4747
> [!NOTE]
4848
> To save the project file with encoding, first unload the project. The **Save File As** option isn't enabled until you unload the project.
4949
50-
::: moniker range=">= vs-2022"
50+
51+
::: moniker range="visualstudio"
52+
53+
## Set the default encoding
54+
55+
You can set the default encoding for saving files.
56+
57+
1. In the **Tools** > **Options** pane, expand the **All Settings** > **Environment** > **Documents** section.
58+
59+
1. Select the **Save files with a specific encoding** checkbox.
60+
61+
1. In the **Save encoding** dropdown, select your desired default encoding type.
62+
63+
::: moniker-end
64+
::: moniker range="vs-2022"
65+
5166
## Set the default encoding
5267

5368
Starting in Visual Studio 2022 version 17.13 Preview 1, you can set the default encoding for saving files.
5469

55-
To set the default, choose **Tools** > **Options** > **Environment**, **Documents**. Next, select **Save files with a specific encoding**, and then select the encoding you want as the default.
70+
1. In the **Tools** > **Options** dialog, expand the **Environment** > **Documents** section.
71+
72+
1. Select the **Save files with a specific encoding** checkbox.
73+
74+
1. In the **Save encoding** dropdown, select your desired default encoding type.
75+
76+
1. Select **OK**.
77+
5678
::: moniker-end
5779

5880
## Open encoded file with project

‎docs/ide/quick-actions.md‎

Lines changed: 15 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Quick Actions, light bulbs, and screwdrivers
33
description: Use a single Quick Action in Visual Studio to refactor, generate, or modify your C#, C++, or Visual Basic code files to apply updates and fixes or generate code.
4-
ms.date: 03/26/2025
4+
ms.date: 11/17/2025
55
ms.update-cycle: 180-days
66
ms.topic: concept-article
77
author: Mikejo5000
@@ -78,10 +78,22 @@ If there's an error in your code, and Visual Studio has a recommended fix, you s
7878
> [!TIP]
7979
> You can turn off some of the code fix Quick Actions. For more information, see [Disable source code analysis for .NET](../code-quality/disable-code-analysis.md).
8080
81-
::: moniker range=">=visualstudio"
81+
::: moniker range=">=vs-2022"
82+
8283
## Configure Quick Actions
8384

84-
You can configure whether to show Quick Actions when hovering over code by selecting **Tools > Options > Languages > Defaults > General**, and then selecting or deselecting **Show Quick Info on hover**.
85+
You can configure whether to show Quick Actions when hovering over code by setting the **Show Quick Info on hover** option.
86+
87+
::: moniker-end
88+
::: moniker range="visualstudio"
89+
90+
Open the **Tools** > **Options** pane and expand the **All Settings** > **Text Editor** > **General** section. Select or clear the **Show Quick Info on hover** checkbox.
91+
92+
::: moniker-end
93+
::: moniker range="vs-2022"
94+
95+
Open the **Tools** > **Options** dialog and expand the **Text Editor** > **All Languages** > **General** section. Select or clear the **Show Quick Info on hover** checkbox.
96+
8597
::: moniker-end
8698

8799
::: moniker range=">=vs-2022"

‎docs/ide/reference/command-prompt-powershell.md‎

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Command-Line Shells & Prompt For Developers
33
description: Learn about the two command-line shells for developers in Visual Studio, the Developer Command Prompt and the Developer PowerShell.
44
author: Mikejo5000
55
ms.author: mikejo
6-
ms.date: 09/23/2025
6+
ms.date: 11/18/2025
77
ms.topic: article
88
helpviewer_keywords:
99
- "Visual Studio command prompt"
@@ -237,12 +237,16 @@ Start the Developer PowerShell for the Community Edition of [Visual Studio 2022
237237

238238
For Developer PowerShell, the starting directory of the shell is the Visual Studio Project Location. This default locale overrides any other paths, such as working directory. This behavior can be turned off by using the command-line argument `-SkipAutomaticLocation`. This can be useful if you want the shell to stay in the current directory after initialization.
239239

240-
::: moniker range="vs-2019"
241-
The Project Location can be adjusted in **Tools** > **Options** > **Projects &amp; Solutions** > **Project Location**.
240+
::: moniker range="visualstudio"
241+
The Project Location can be adjusted in the **Tools** > **Options** pane in the **All Settings** > **Projects and Solutions** > **Locations** section.
242242
::: moniker-end
243243

244-
::: moniker range=">=vs-2022"
245-
The Project Location can be adjusted in **Tools** > **Options** > **Projects &amp; Solutions** > **Locations**.
244+
::: moniker range="vs-2022"
245+
The Project Location can be adjusted in the **Tools** > **Options** dialog in the **Projects and Solutions** > **Locations** section.
246+
::: moniker-end
247+
248+
::: moniker range="vs-2019"
249+
The Project Location can be adjusted in **Tools** > **Options** > **Projects &amp; Solutions** > **Project Location**.
246250
::: moniker-end
247251

248252
> [!TIP]

0 commit comments

Comments
 (0)