Merge pull request #14706 from MicrosoftDocs/main

Auto Publish – main to live - 2025-11-26 23:00 UTC

Author: learn-build-service-prod[bot]

docs/ide/encodings-and-line-breaks.md

@@ -1,7 +1,7 @@
 ---
 title: Encoding and line break characters
 description: Explore the special characters that Visual Studio interprets as line breaks and separators and understand how to configure and maintain your encoding and line break.
-ms.date: 12/17/2024
+ms.date: 11/13/2025
 ms.topic: concept-article
 f1_keywords:
 - vs.Encoding
@@ -56,6 +56,19 @@ You can also place the **Advanced Save Options** command directly on the **File*
 
 For more information, see [Customize menus and toolbars](./how-to-customize-menus-and-toolbars-in-visual-studio.md#customize-a-menu-or-a-toolbar).
 
+:::moniker range="visualstudio"
+
+## Encoding in the editor margin
+
+The editor bottom margin features an encoding widget that displays the current automatically detected encoding for the file, but also lets you change it. You can reopen or save the current file with a different encoding.
+
+:::image type="content" alt-text="Screenshot showing editor bottom margin with the encoding widget highlighted." source="media/visualstudio/encoding-in-margin.png":::
+
+If you choose to reopen or save the file, a dialog appears that lets you select an encoding. For help deciding what encoding you need, see [Character and data encoding](/globalization/encoding/encoding-overview).
+
+:::moniker-end
+
 ## Related content
 
 - [Features of the code editor](./writing-code-in-the-code-and-text-editor.md)
+- [Character and data encoding](/globalization/encoding/encoding-overview)

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

@@ -1,8 +1,10 @@
 ---
 title: Save and open files with encoding
 description: Learn how to save and open files with specific encoding in Visual Studio, and ensure files open correctly in subsequent use.
-ms.date: 11/13/2025
+ms.date: 11/14/2025
 ms.topic: how-to
+f1_keywords:
+- vs.advancedsaveoptions
 helpviewer_keywords:
 - Unicode, bidirectional language support
 - files, encoding
@@ -26,7 +28,23 @@ You can save files with specific character encoding in Visual Studio to support
 
 ## Save file with encoding
 
-Follow these steps to save your file with encoding:
+:::moniker range="visualstudio"
+
+Follow these steps to save your file with encoding. This procedure overwrites the file with its previous encoding.
+
+1. In the editor bottom margin, on the bottom right, click on the encoding widget.
+
+1. To save the file with a different encoding, choose **Save with Encoding**.
+
+   A dialog box appears with a dropdown list of available encodings. 
+
+   :::image type="content" alt-text="Screenshot of encodings dialog box." source="media/visualstudio/encoding-dialog-box.png":::
+
+1. Choose the encoding and select **OK**. The file is saved.
+
+:::moniker-end
+
+Follow these steps to save your file under a new filename with encoding:
 
 1. In Visual Studio, select **File** > **Save <Filename\> As** for the file you want to save.
 

docs/ide/media/visualstudio/editor-bottom-margin-context-menu.png

@@ -1,7 +1,7 @@
 ---
 title: Toolbox window
 description: Learn about the Toolbox window and how it displays controls that you can add to Visual Studio projects.
-ms.date: 06/01/2020
+ms.date: 11/26/2025
 ms.topic: reference
 f1_keywords:
 - vs.toolbox.general

docs/ide/media/visualstudio/encoding-dialog-box.png

@@ -65,7 +65,11 @@ You can find many advanced features on the **Edit** > **Advanced** menu on the t
 
 ## Navigate and find code
 
-You can move around the code editor in several different ways, including navigating backward and forward to previous insertion points, viewing the definition of a type or member, and jumping to a specific method using the navigation bar. For more information, see [Navigate code](navigating-code.md).
+You can move around the code editor in several different ways, including jumping to a specific line number, navigating backward and forward to previous insertion points, viewing the definition of a type or member, and jumping to a specific method using the navigation bar. For more information, see [Navigate code](navigating-code.md).
+
+:::moniker range="visualstudio"
+To jump to a line number, press **Ctrl**+**G** or click the line and column numbers in the editor's bottom margin.
+:::moniker-end
 
 You can also set bookmarks to mark lines in your code so that you can quickly return to a specific location, or jump back and forth between locations. To learn more, see [Bookmark code](setting-bookmarks-in-code.md).
 
@@ -103,6 +107,24 @@ You can share your Visual Studio settings with another developer, have your sett
 
 To define new hotkeys or redefine existing hotkeys, go to **Tools** > **Options** > **Environment** > **Keyboard**. For more information about hotkeys, see [Keyboard shortcuts](../ide/default-keyboard-shortcuts-in-visual-studio.md).
 
+:::moniker range="visualstudio"
+
+The bottom margin of the editor contains some customization controls.
+
+You can easily change the default indentation style from tabs to spaces to vice versa by clicking on SPC or TAB. The actual number of spaces is configurable in **Tools** > **Options**, under **All Settings** > **Text Editor** > **All languages** > **Tabs**.
+
+You can also change the default end-of-line codes from CR LF, the standard on Windows, to a different setting for better compatibility with other operating systems.
+
+The bottom margin of the editor can also be customized. Right-click on an unused area of the margin to open the context menu, which lets you select or unselect each  control element.
+
+:::image type="content" alt-text="Screenshot of the bottom margin context menu, showing optional control elements." source="./media/visualstudio/editor-bottom-margin-context-menu.png":::
+
+You can also change these settings in the **Tools** > **Options** pane, under **All Settings** > **Text Editor** > **General**. To control the bottom margin elements, make your selections under **Show editing context in the editor**.
+
+:::image type="content" alt-text="Screenshot of Tools > Options experience under Text Editor > General, with the setting Show editing context in the editor highlighted." source="./media/visualstudio/tools-options-show-editing-context-in-the-editor.png":::
+
+:::moniker-end
+
 For JavaScript-specific editor options, see [JavaScript editor options](/previous-versions/visualstudio/visual-studio-2017/ide/reference/options-text-editor-javascript-formatting).
 
 ## Related content

docs/ide/media/visualstudio/encoding-in-margin.png

@@ -1,7 +1,7 @@
 ---
 title: "Create an ASP.NET Core app with React"
 description: Create an ASP.NET Core project to serve as an API backend and a React project to provide the user interface in Visual Studio.
-ms.date: 04/09/2025
+ms.date: 11/26/2025
 ms.topic: tutorial
 ms.devlang: javascript
 author: mikejo5000
@@ -133,7 +133,9 @@ If you don't see the weather forecast data in the browser, see [Troubleshooting]
    }
    ```
 
-1. To publish, right click the ASP.NET Core project, choose **Publish**, and select options to match your desired publish scenario, such as Azure, publish to a folder, etc.
+1. Right-click the ASP.NET Core project, choose **Publish**, and select options to match your desired publish scenario, such as Azure, publish to a folder, etc.
+
+1. After the publish profile is created, choose **Publish** in the Publish tab to publish the project.
 
    The publish process takes more time than it does for just an ASP.NET Core project, since the `npm run build` command gets invoked when publishing. The [BuildCommand](../javascript/javascript-project-system-msbuild-reference.md#buildcommand) runs `npm run build` by default.
 

docs/ide/media/visualstudio/tools-options-show-editing-context-in-the-editor.png

@@ -1,7 +1,7 @@
 ---
 title: "Create an ASP.NET Core app with Vue"
 description: Create an ASP.NET Core project to serve as an API backend and a Vue project to provide the user interface in Visual Studio.
-ms.date: 4/09/2025
+ms.date: 11/26/2025
 ms.topic: tutorial
 ms.devlang: javascript
 author: mikejo5000
@@ -136,7 +136,9 @@ Starting in Visual Studio 2022 version 17.3, you can publish the integrated solu
    }
    ```
 
-1. To publish, right click the ASP.NET Core project, choose **Publish**, and select options to match your desired publish scenario, such as Azure, publish to a folder, etc.
+1. Right-click the ASP.NET Core project, choose **Publish**, and select options to match your desired publish scenario, such as Azure, publish to a folder, etc.
+
+1. After the publish profile is created, choose **Publish** in the Publish tab to publish the project.
 
    The publish process takes more time than it does for just an ASP.NET Core project, since the `npm run build` command gets invoked when publishing. The [BuildCommand](../javascript/javascript-project-system-msbuild-reference.md#buildcommand) runs `npm run build` by default.