Repo sync for protected branch

.whatsnew.json

@@ -10,7 +10,7 @@
         "labels": [
             "-label:CLA"
         ],
-        "minAdditionsToFile": 10
+        "minAdditionsToFile": 2
     },
     "areas": [
         {

docs/debugger/adapt-to-removal-of-windows-arm32-dotnet-debugging.md

@@ -0,0 +1,45 @@
+---
+title: "Adapt to removal of Windows Arm32 .NET debugging"
+description: Provides guidance on how to adapt to the removal of Windows Arm32 .NET Debugging support
+ms.date: "12/12/2024"
+ms.topic: "error-reference"
+dev_langs:
+  - "CSharp"
+  - "VB"
+  - "FSharp"
+author: "mikejo5000"
+ms.author: "mikejo"
+manager: mijacobs
+ms.subservice: debug-diagnostics
+---
+
+# Adapt to removal of Windows Arm32 .NET debugging
+
+.NET support for Windows on Arm32 has ended. Debugging support for this platform will be removed from Visual Studio 2022 starting with the 17.14 update. This article lists potential options for customers currently debugging .NET Code on  Windows Arm32. 
+
+
+## Option 1: Run code in an Arm64 process 
+
+If your device runs Arm64 Windows or can be upgraded to it, the easiest way is to migrate the debugged process from Arm32 to Arm64. How to manage the switch to Arm64 depends on the type of project you're using: 
+
+* For Universal Windows Platform (UWP) apps, see [Update app architecture from Arm32 to Arm64](/windows/arm/arm32-to-arm64). 
+* For processes that have their own native executable that's self-hosting the .NET Runtime, the native project needs to be configured to target Arm64. 
+* If the executable project is a .NET project, then something is likely specifying the `RuntimeIdentifier` MSBuild property. `RuntimeIdentifier` should be updated to target `win-arm64` instead of `win-arm` (or similar runtime IDs). 
+
+
+## Option 2: Use an older version of Visual Studio 
+
+Visual Studio 17.12 can be used from the Long-Term Servicing Channel (LTSC). For more information, see [Visual Studio Product Lifecycle and Servicing](/visualstudio/productinfo/vs-servicing). 
+
+
+## Option 3: Start without debugging 
+
+If you have a project that you still want to run but doesn't require debugging, use **Debug->Start without debugging** to run the project. Since the debugger isn't available, you would need to diagnose any problems by using logging. 
+
+> [!NOTE]
+> This option is not recommended since .NET support for Windows on Arm32 has ended.
+
+
+## Option 4: Target Linux 
+
+The .NET Runtime continues to support Arm32 Linux. For IoT hardware that isn't capable of running Arm64 Windows but is capable of running Arm32 Linux, the only supported path for running .NET Code on that hardware would be to switch to Linux.

docs/debugger/toc.yml

@@ -294,6 +294,8 @@
         href: error-unable-to-connect-to-the-machine-name-the-machine-cannot-be-found-on-the-network.md
       - name: Remote machine does not appear in a Remote Connections dialog
         href: error-remote-machine-does-not-appear-in-a-remote-connections-dialog.md
+      - name: Adapt to removal of Windows Arm32 .NET debugging
+        href: adapt-to-removal-of-windows-arm32-dotnet-debugging.md
   - name: Attach to process
     items:
     - name: Attach to running processes with the debugger

docs/extensibility/how-to-provide-brokered-service.md

@@ -387,7 +387,7 @@ As not all combinations are valid, we recommend either of these combinations:
 <xref:Microsoft.ServiceHub.Framework.ServiceJsonRpcDescriptor.Formatters.MessagePack> | <xref:Microsoft.ServiceHub.Framework.ServiceJsonRpcDescriptor.MessageDelimiters.BigEndianInt32LengthHeader> | High performance
 <xref:Microsoft.ServiceHub.Framework.ServiceJsonRpcDescriptor.Formatters.UTF8> (JSON) | <xref:Microsoft.ServiceHub.Framework.ServiceJsonRpcDescriptor.MessageDelimiters.HttpLikeHeaders> | Interop with other JSON-RPC systems
 
-By specifying the `MultiplexingStream.Options` object as the final parameter, the RPC connection shared between client and service is just one channel on a [MultiplexingStream](https://github.com/AArnott/Nerdbank.Streams/blob/main/doc/MultiplexingStream.md), which is shared with the JSON-RPC connection to [enable efficient transfer of large binary data over JSON-RPC](https://github.com/microsoft/vs-streamjsonrpc/blob/main/doc/oob_streams.md).
+By specifying the `MultiplexingStream.Options` object as the final parameter, the RPC connection shared between client and service is just one channel on a [MultiplexingStream](https://dotnet.github.io/Nerdbank.Streams/docs/MultiplexingStream.html), which is shared with the JSON-RPC connection to [enable efficient transfer of large binary data over JSON-RPC](https://github.com/microsoft/vs-streamjsonrpc/blob/main/doc/oob_streams.md).
 
 The <xref:StreamJsonRpc.ExceptionProcessing.ISerializable?displayProperty=nameWithType> strategy causes exceptions thrown from your service to be serialized and preserved as the <xref:System.Exception.InnerException?displayProperty=nameWithType> to the <xref:StreamJsonRpc.RemoteInvocationException> thrown on the client.
 Without this setting, less detailed exception information is available on the client.

docs/ide/whats-new-visual-studio-docs.md

@@ -1,7 +1,7 @@
 ---
 title: "What's new in Visual Studio docs"
 description: Discover recent changes in the Visual Studio documentation, including updated articles about getting started, the IDE, and deployment.
-ms.date: 12/02/2024
+ms.date: 12/12/2024
 helpviewer_keywords:
   - "Visual Studio, what's new, docs"
   - "what's new [Visual Studio]"
@@ -17,6 +17,12 @@ Welcome to what's new in Visual Studio docs. The following sections provide deta
 
 ## November 2024
 
+### Azure
+
+**Updated articles**
+
+- [Sign in with an Azure subscription](../azure/how-to-sign-in-with-azure-subscription.md) - Link to tenant filtering
+
 ### Debugger
 
 **New articles**
@@ -28,9 +34,23 @@ Welcome to what's new in Visual Studio docs. The following sections provide deta
 
 **Updated articles**
 
-- [Use the right type of breakpoint](../debugger/using-breakpoints.md) - Refactor breakpoints article and incorporate review feedback
+- [Use the right type of breakpoint](../debugger/using-breakpoints.md)
+  - Add link to breakpoints article for new users
+  - Refactor breakpoints article and incorporate review feedback
+  - Add information on export and import of breakpoint groups
+- [FAQ - Debugger feature finder](../debugger/find-your-debugging-task.yml) - Refactor breakpoints article and incorporate review feedback
+- [View and change variable values with data tips in the code editor](../debugger/view-data-values-in-data-tips-in-the-code-editor.md) - Refactor breakpoints article and incorporate review feedback
+- [Attach to a process running on a Docker container](../debugger/attach-to-process-running-in-docker-container.md) - Updates for Attach to Process for Docker with WSL scenarios
 - [Use the Memory windows in the Visual Studio debugger (C#, C++, Visual Basic, F#)](../debugger/memory-windows.md) - Update article on Memory windows
+- [IDiaSymbol::get_value](../debugger/debug-interface-access/idiasymbol-get-value.md) - Update example usage for IDiaSymbol::get_value
+- [Remote Debug ASP.NET on a Remote IIS Computer](../debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md) - Add security information to remote debugging IIS articles
+- [Remote Debug ASP.NET Core on a Remote IIS Computer in Visual Studio](../debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md) - Add security information to remote debugging IIS articles
+- [Remote Debug ASP.NET Core on IIS using an Azure VM from Visual Studio](../debugger/remote-debugging-azure.md) - Add security information to remote debugging IIS articles
+- [Debug your app with GitHub Copilot in Visual Studio](../debugger/debug-with-copilot.md) - Add Copilot content for Quick Actions light bulb
+- [Pass command-line arguments while debugging (C++)](../debugger/specify-command-line-arguments.md) - fix title
+- [Inspect variables in the Autos and Locals windows](../debugger/autos-and-locals-windows.md) - Update debugger content for viewing return values
 - [First look at the Visual Studio Debugger](../debugger/debugger-feature-tour.md) - Update debugger content for viewing return values
+- [Tabular visualizers in Visual Studio](../debugger/view-data-in-tabular-visualizer.md) - Add information about IntelliSense for IEnumerable visualizer
 - [IDiaStackWalkHelper::pdataForVA](../debugger/debug-interface-access/idiastackwalkhelper-pdataforva.md) - Add docs for 3 missing IDiaStackWalkHelper functions
 - [IDiaStackWalkHelper](../debugger/debug-interface-access/idiastackwalkhelper.md) - Add docs for 3 missing IDiaStackWalkHelper functions
 - [SymTagEnum](../debugger/debug-interface-access/symtagenum.md) - Fix broken links due to improper code escapes
@@ -39,29 +59,65 @@ Welcome to what's new in Visual Studio docs. The following sections provide deta
 
 **Updated articles**
 
+- [First look at deployment in Visual Studio](../deployment/deploying-applications-services-and-components.md) - Review and update
 - [Visual Studio Installer Projects Extension and .NET](../deployment/installer-projects-net-core.md) - Update .NET installer projects article
 
 ### Extensibility
 
 **Updated articles**
 
+- [Use Visual Studio editor extensibility](../extensibility/visualstudio.extensibility/editor/editor.md)
+  - Fix missing and incorrect links
+  - Add 17.12 documentation to VisualStudio.Extensibility
+- [Sign CLI Reference for VSIX Packages](../extensibility/dotnet-sign-cli-reference-vsix.md) - VSIX Signing:  fix Sign CLI examples
 - [Overview](../extensibility/visualstudio.extensibility/diagnostics/visualstudio-extensibility-diagnostics-extension.md) - Add 17.12 documentation to VisualStudio.Extensibility
-- [Use Visual Studio editor extensibility](../extensibility/visualstudio.extensibility/editor/editor.md) - Add 17.12 documentation to VisualStudio.Extensibility
-- [Write to the Visual Studio output window](../extensibility/visualstudio.extensibility/output-window/output-window.md) - Updating docs for VS.Extensibility output window in 17.12
+- [Write to the Visual Studio output window](../extensibility/visualstudio.extensibility/output-window/output-window.md)
+  - Add 17.12 documentation to VisualStudio.Extensibility
+  - Updating docs for VS.Extensibility output window in 17.12
 
 ### IDE
 
 **Updated articles**
 
+- [What is Class Designer?](../ide/class-designer/designing-and-viewing-classes-and-types.md) - Update/fix class designer instructions
+- [Quick Actions](../ide/quick-actions.md)
+  - Add Copilot content for Quick Actions light bulb
+  - Add instruction for invoking quick actions, refactor
+- [What's new in Visual Studio 2022](../ide/whats-new-visual-studio-2022.md) - Update for 17.12
+- [Find code changes and other history with CodeLens](../ide/find-code-changes-and-other-history-with-codelens.md) - Add instructions for showing file-level indicators for CodeLens
 - [Code style preferences](../ide/code-styles-and-code-cleanup.md) - Clarify code cleanup instructions
-- [Create, work with, and delete Visual Studio projects and solutions](../ide/creating-solutions-and-projects.md) - Add new copy between VS instances features
-- [Configure trust settings for files and folders](../ide/reference/trust-settings.md) - Add VS 17.12 feature MOTW (Mark of the Web)
+- [Create, work with, and delete Visual Studio projects and solutions](../ide/creating-solutions-and-projects.md) - Add new copy between Visual Studio instances features
+- [Get better answers by setting the context for GitHub Copilot Chat in Visual Studio](../ide/copilot-chat-context.md) - Add guided chat experience for 17.12
+- [Visual Studio Developer Command Prompt and Developer PowerShell](../ide/reference/command-prompt-powershell.md) - Update project location instructions
+- [What is the GitHub Copilot Chat experience for Visual Studio?](../ide/visual-studio-github-copilot-chat.md) - Add code referencing update
+- [Configure trust settings for files and folders](../ide/reference/trust-settings.md) - Add Visual Studio 17.12 feature motw
 - [Find in Files](../ide/find-in-files.md) - Update Find in Files for 17.12 for refresh and modify options
 - [Use Visual Studio search](../ide/visual-studio-search.md) - Update for 17.12 for new All In One Search features
-- [Quick Actions](../ide/quick-actions.md) - Add instruction for invoking quick actions, refactor
+- [Error List window](../ide/reference/error-list-window.md) - Copy from error list: feature update for 17.12
 - [Fonts and Colors, Environment, Options dialog box](../ide/reference/fonts-and-colors-environment-options-dialog-box.md) - Add collapsible text indicators to table
+- [Change fonts, colors, and themes in Visual Studio](../ide/how-to-change-fonts-and-colors-in-visual-studio.md) - Preserve font settings across themes
 - [Sign in to Visual Studio with accounts that require multifactor authentication (MFA)](../ide/work-with-multi-factor-authentication.md) - Add access denied text
 
+### JavaScript
+
+**Updated articles**
+
+- [MSBuild reference for the JavaScript Project System](../javascript/javascript-project-system-msbuild-reference.md) - Update example code for ShouldRunBuildScript in JS projects
+- [Tutorial: Create an ASP.NET Core app with Angular in Visual Studio](../javascript/tutorial-asp-net-core-with-angular.md) - Add links related to publish output for ASP.NET Core and JSTS
+- [Tutorial: Create an ASP.NET Core app with React in Visual Studio](../javascript/tutorial-asp-net-core-with-react.md)
+  - Add links related to publish output for ASP.NET Core and JSTS
+  - Updates for JS project templates related to Vite CLI
+- [Tutorial: Create an ASP.NET Core app with Vue in Visual Studio](../javascript/tutorial-asp-net-core-with-vue.md)
+  - Add links related to publish output for ASP.NET Core and JSTS
+  - Updates for JS project templates related to Vite CLI
+
+### MSBuild
+
+**Updated articles**
+
+- [Task writing](../msbuild/task-writing.md) - Add section with link to packaging info
+- [MSBuild](../msbuild/msbuild.md) - Review and update
+
 ### Profiling
 
 **Updated articles**
@@ -74,6 +130,14 @@ Welcome to what's new in Visual Studio docs. The following sections provide deta
 
 - [Debug and analyze unit tests with Test Explorer](../test/debug-unit-tests-with-test-explorer.md) - Add content for debugging unit tests with Copilot
 
+### Version control
+
+**Updated articles**
+
+- [Make a Git commit in Visual Studio](../version-control/git-make-commit.md) - Add note about rename notification
+- [Create a Git repository from Visual Studio](../version-control/git-create-repository.md) - Updates for 17.12 support for internal repo
+- [About Git in Visual Studio](../version-control/git-with-visual-studio.md) - Add doc for Copy GitHub Permalink feature
+
 ### Community contributors
 
 The following people contributed to the Visual Studio docs during this period. Thank you! Learn how to contribute by following the links under "Get involved" in the [what's new landing page](index.yml).
@@ -193,8 +257,8 @@ The following people contributed to the Visual Studio docs during this period. T
 
 **Updated articles**
 
-- [Case study: Isolate a performance issue (C#, Visual Basic, F#)](../profiling/isolate-performance-issue.md) - Update Copilot information in the VS Profiling case studies
-- [Case Study: Beginner's guide to optimizing code and reducing compute costs (C#, Visual Basic, C++, F#)](../profiling/optimize-code-using-profiling-tools.md) - Update Copilot information in the VS Profiling case studies
+- [Case study: Isolate a performance issue (C#, Visual Basic, F#)](../profiling/isolate-performance-issue.md) - Update Copilot information in the Visual Studio Profiling case studies
+- [Case Study: Beginner's guide to optimizing code and reducing compute costs (C#, Visual Basic, C++, F#)](../profiling/optimize-code-using-profiling-tools.md) - Update Copilot information in the Visual Studio Profiling case studies
 - [Identify hot paths with a flame graph (C#, Visual Basic, C++, F#)](../profiling/flame-graph.md) - Update Flame Graph article with additional context and information
 
 ### Windows