MicrosoftDocs · learn-build-service-prod · May 1, 2026 · Apr 28, 2026 · Apr 28, 2026 · Apr 28, 2026
diff --git a/docs/debugger/edit-and-continue-visual-basic.md b/docs/debugger/edit-and-continue-visual-basic.md
@@ -26,7 +26,6 @@ ms.custom: awp-ai
 Hot Reload, previously called Edit and Continue, is a feature for Visual Basic debugging that enables you to change your code while it's executing in Break mode. After code edits have been applied, you can resume code execution with the new edits in place and see the effect.
 ::: moniker-end
 
-
 You can use Hot Reload whenever you enter Break mode. In Break mode, the instruction pointer, a yellow arrowhead in the source window, points to the line containing an executable statement in a method or property body that will be executed next.
 
 When you make an unauthorized edit, the change is marked with a purple wavy underline and a task is displayed in the Task List. You must undo an unauthorized edit if you want to continue to use Hot Reload. Certain unauthorized edits may be permitted if done outside Hot Reload. If you want to retain the results of such an unauthorized edit, you must stop debugging and restart your application.

diff --git a/docs/debugger/supported-code-changes-cpp.md b/docs/debugger/supported-code-changes-cpp.md
@@ -1,7 +1,7 @@
 ---
 title: "Supported Code Changes (C++)"
-description: Understand what code changes are supported when you're using the Edit and Continue feature while debugging a C++ project in Visual Studio.
-ms.date: "11/05/2025"
+description: Understand what code changes are supported when you're using the Hot Reload feature while debugging a C++ project in Visual Studio.
+ms.date: "04/28/2026"
 ms.topic: concept-article
 dev_langs:
   - "C++"
@@ -22,9 +22,9 @@ ms.subservice: debug-diagnostics
 ---
 # Supported Code Changes (C++)
 
-Edit and Continue for C++ projects handles most types of code changes. However, some changes can't be applied during program execution. To apply these changes, you must stop execution and build a fresh version of the code.
+The Hot Reload mechanism, previously called Edit and Continue, handles most types of code changes. However, some changes can't be applied during program execution. To apply these changes, you must stop execution and build a fresh version of the code.
 
-See [Edit and Continue (C++)](../debugger/edit-and-continue-visual-cpp.md) for information about working with Edit and Continue for C++ in Visual Studio.
+See [Hot Reload (C++)](../debugger/edit-and-continue-visual-cpp.md) for information about working with Hot Reload for C++ in Visual Studio.
 
 ## <a name="BKMK_Requirements"></a> Requirements
 
@@ -96,11 +96,11 @@ The following C/C++ changes can't be applied during a debugging session. If you
    - When lambdas have a static or global member.
    - When you pass lambdas to an `std::function`. This method causes a genuine ODR violation and results in C1092.
 
-- Edit and Continue doesn't update static libraries. If you make a change in a static library, execution continues with the old version and no warning is issued.
+- Hot Reload doesn't update static libraries. If you make a change in a static library, execution continues with the old version and no warning is issued.
 
 ## <a name="BKMK_Unsupported_scenarios"></a> Unsupported scenarios
 
-Edit and Continue for C/C++ is unavailable in the following debugging scenarios:
+Hot Reload for C/C++ is unavailable in the following debugging scenarios:
 
 - Debugging native apps compiled with [/Zo (Enhance Optimized Debugging)](/cpp/build/reference/zo-enhance-optimized-debugging)
 
@@ -122,14 +122,14 @@ Edit and Continue for C/C++ is unavailable in the following debugging scenarios:
 
 - Debugging an old version of your code after a new version failed to build because of build errors.
 
-- Using a custom compiler (*cl.exe*) path. For security reasons, for recompilation of a file during Edit and Continue, Visual Studio always uses the installed compiler. If you're using a custom compiler path (for example, through a custom `$(ExecutablePath)` variable in your `*.props` file), a warning is displayed and Visual Studio falls back to using the installed compiler of the same version/architecture.
+- Using a custom compiler (*cl.exe*) path. For security reasons, for recompilation of a file during Hot Reload, Visual Studio always uses the installed compiler. If you're using a custom compiler path (for example, through a custom `$(ExecutablePath)` variable in your `*.props` file), a warning is displayed and Visual Studio falls back to using the installed compiler of the same version/architecture.
 
-- Legacy Architectures/MSVC toolsets. With the MSVC v140 toolset, the default debugger supports Edit and Continue with both X86 and X64 applications. Legacy toolsets support only X86 applications. Toolsets older than MSVC v120 should use the legacy debugger by checking "_Debug > Options > General >_ Use Native Compatibility Mode" in order to use Edit and Continue.
+- Legacy Architectures/MSVC toolsets. With the MSVC v140 toolset, the default debugger supports Hot Reload with both X86 and X64 applications. Legacy toolsets support only X86 applications. Toolsets older than MSVC v120 should use the legacy debugger by checking "_Debug > Options > General >_ Use Native Compatibility Mode" in order to use Edit and Continue.
 
 
 ## <a name="BKMK_IDL_attribute_limitations"></a> IDL attribute limitations
 
-Edit and Continue doesn't regenerate interface definition language (IDL) files. Therefore, changes to IDL attributes aren't reflected while you're debugging. To see the result of changes to IDL attributes, you must stop debugging and rebuild your app. Edit and Continue doesn't generate an error or warning if IDL attributes have changed. For more information, see [IDL Attributes](/cpp/windows/idl-attributes).
+Hot Reload doesn't regenerate interface definition language (IDL) files. Therefore, changes to IDL attributes aren't reflected while you're debugging. To see the result of changes to IDL attributes, you must stop debugging and rebuild your app. Hot Reload doesn't generate an error or warning if IDL attributes have changed. For more information, see [IDL Attributes](/cpp/windows/idl-attributes).
 
 ## <a name="BKMK_Diagnosing_issues"></a> Diagnosing issues
 
@@ -144,9 +144,9 @@ If your scenario doesn't fit any of the conditions mentioned above, you can gath
     ::: moniker-end
 
 
-Setting this value at the start of a debug session causes the various components of Edit and Continue to spew verbose logging to the **Output Window** > **Debug** pane.
+Setting this value at the start of a debug session causes the various components of Hot Reload to spew verbose logging to the **Output Window** > **Debug** pane.
 
 ## Related content
 
-- [Edit and Continue (C++)](../debugger/edit-and-continue-visual-cpp.md)
-- [Configure Edit and Continue](../debugger/how-to-enable-and-disable-edit-and-continue.md)
+- [Hot Reload (C++)](../debugger/edit-and-continue-visual-cpp.md)
+- [Configure Hot Reload](../debugger/how-to-enable-and-disable-edit-and-continue.md)
diff --git a/docs/debugger/supported-code-changes-csharp.md b/docs/debugger/supported-code-changes-csharp.md
@@ -1,7 +1,7 @@
 ---
 title: "Supported Code Changes (C# and Visual Basic)"
-description: Understand what code changes are supported when you're using the Edit and Continue feature while debugging a C# or Visual Basic project in Visual Studio.
-ms.date: "3/21/2025"
+description: Understand what code changes are supported when you're using the Hot Reload feature while debugging a C# or Visual Basic project in Visual Studio.
+ms.date: "4/28/2026"
 ms.topic: concept-article
 dev_langs:
   - "CSharp"
@@ -40,7 +40,7 @@ The following table shows the changes that might be made to C# and Visual Basic
 
 
 > [!NOTE]
-> Newer language features such as string interpolation and null-conditional operators are generally supported by Edit and Continue. For the most current information, see the [Enc Supported Edits](https://github.com/dotnet/roslyn/blob/main/docs/wiki/EnC-Supported-Edits.md) page. For .NET Framework, the supported features are a subset of the listed features and are dependent on the compiler version.
+> Newer language features such as string interpolation and null-conditional operators are generally supported by Edit and Continue. For the most current information, see the [Supported Edits](https://github.com/dotnet/roslyn/blob/main/docs/wiki/EnC-Supported-Edits.md) page. For .NET Framework, the supported features are a subset of the listed features and are dependent on the compiler version.
 
 ::: moniker range=">=vs-2022"
 
@@ -113,9 +113,7 @@ Unsupported applications or platforms include:
 
 - F#
 - .NET Native
-- Silverlight 5
 - Windows 8.1
-- Xamarin.Forms (iOS and Android)
 
 For ASP.NET and ASP.NET Core, editing isn't supported for the following file types:
 
@@ -124,7 +122,6 @@ For ASP.NET and ASP.NET Core, editing isn't supported for the following file typ
 - .ascx
 ::: moniker-end
 
-
 ## Unsupported scenarios
 
 Edit and Continue isn't available in the following debugging scenarios:
@@ -151,6 +148,5 @@ Edit and Continue isn't available in the following debugging scenarios:
 
 ## Related content
 
-- [Edit and Continue (Visual C#)](../debugger/edit-and-continue-visual-csharp.md)
-- [How to: Use Edit and Continue (C#)](/visualstudio/debugger/edit-and-continue-visual-csharp)
-- [Configure Edit and Continue](../debugger/how-to-enable-and-disable-edit-and-continue.md)
+- [Hot Reload (Visual C#)](../debugger/edit-and-continue-visual-csharp.md)
+- [Configure Hot Reload](../debugger/how-to-enable-and-disable-edit-and-continue.md)
diff --git a/docs/deployment/clickonce-security-and-deployment.md b/docs/deployment/clickonce-security-and-deployment.md
@@ -1,7 +1,7 @@
 ---
 title: "ClickOnce Deployment and Security"
 description: Learn about Visual Studio support for ClickOnce, a deployment technology that enables you to create self-updating Windows-based applications.
-ms.date: "04/25/2025"
+ms.date: "04/28/2026"
 ms.topic: concept-article
 dev_langs:
   - "VB"

diff --git a/docs/python/overview-of-python-tools-for-visual-studio.md b/docs/python/overview-of-python-tools-for-visual-studio.md
@@ -155,6 +155,8 @@ For more information, see:
 - [Python/C++ mixed-mode debugging](debugging-mixed-mode-c-cpp-python-in-visual-studio.md)
 - [Remote debugging on Linux](debugging-python-code-on-remote-linux-machines.md)
 - [Feature tour of the Visual Studio debugger](../debugger/debugger-feature-tour.md)
+
+:::moniker range="vs-2022"
 ## Profiling tools with comprehensive reporting
 
 Profiling explores how time is being spent within your application. Visual Studio supports profiling with CPython-based interpreters and includes the ability to compare performance between different profiling runs.
@@ -165,6 +167,8 @@ For more information, see:
 
 - [Python profiling tools](profiling-python-code-in-visual-studio.md)
 - [Visual Studio profiling feature tour](../profiling/profiling-feature-tour.md)
+::: moniker-end
+
 ## Unit testing tools
 
 Discover, run, and manage tests in Visual Studio **Test Explorer**, and easily debug unit tests.

diff --git a/docs/python/profiling-python-code-in-visual-studio.md b/docs/python/profiling-python-code-in-visual-studio.md
@@ -5,7 +5,7 @@ ms.date: 04/18/2024
 ms.topic: how-to
 author: Devdiv-VR
 ms.author: vedhar
-
+monikerRange: '<= vs-2022'
 ms.subservice: python
 
 # CustomerIntent: As a developer, I want to develop Python projects in Visual Studio so I can use debugging and profiling features to check the performance of my Python code.