Merging changes synced from https://github.com/MicrosoftDocs/visualstudio-docs-pr (branch live)

Author: opbld17

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

@@ -2,7 +2,7 @@
 title: "What's new in Visual Studio 2022"
 titleSuffix: ""
 description: "Learn about the new features in Visual Studio 2022."
-ms.date: 11/16/2022
+ms.date: 11/18/2022
 helpviewer_keywords:
   - "Visual Studio, what's new"
   - "what's new [Visual Studio]"
@@ -24,7 +24,7 @@ ms.workload:
 >[!div class="button"]
 >[Download Visual Studio 2022](https://visualstudio.microsoft.com/downloads/)
 
-With [Visual Studio 2022](https://visualstudio.microsoft.com/vs/), you'll always get the best-in-class tools and services available for any developer, any app, and any platform. Whether you're using Visual Studio for the first time or you've been using it for years, there's a lot to like in our newest version!
+With [Visual Studio 2022](https://visualstudio.microsoft.com/vs/), you'll always get the best-in-class tools and services available for any developer, any app, and any platform. Whether you're using Visual Studio for the first time or you've been using it for years, there's a lot to like in our newest version.
 
 Want to see what's new in each updated release from within Visual Studio itself? Now you can! From the menu bar, select **Help** > **What's New** to view recent highlights.
 
@@ -58,7 +58,10 @@ In [Visual Studio 2022](https://devblogs.microsoft.com/visualstudio/visual-studi
 
 ## Build modern apps
 
-Visual Studio 2022 makes it quick and easy to build modern, cloud-based applications with Azure. As well, our new version also has full support for [.NET 6](https://devblogs.microsoft.com/dotnet/announcing-net-6/) and its unified framework for web, client, and mobile apps for both Windows and Mac developers. And, Visual Studio 2022 includes robust support for the C++ workload with new productivity features, C++20 tooling, and [IntelliSense](using-intellisense.md).
+Visual Studio 2022 makes it quick and easy to build modern, cloud-based applications with Azure. As well, our new version also has full support for .NET and its unified framework for web, client, and mobile apps for both Windows and Mac developers. And, Visual Studio 2022 includes robust support for the C++ workload with new productivity features, C++20 tooling, and [IntelliSense](using-intellisense.md).
+
+> [!TIP]
+> To learn more about **.NET 7**, the successor to [.NET 6](/dotnet/core/whats-new/dotnet-6/), see [What's new in .NET 7](/dotnet/core/whats-new/dotnet-7/).
 
 ### Better dev tools for C++ and .NET, and Hot Reload
 
@@ -78,9 +81,9 @@ From real-time & asynchronous collaboration tools to improved insights and produ
 
 ### Git multi-repo support and line-staging support
 
-If you've worked with projects hosted on different Git repositories, you might have used external tools or multiple instances of Visual Studio to connect to them. In [Visual Studio 2022](https://devblogs.microsoft.com/visualstudio/visual-studio-2022-preview-3-now-available/), you can work with a single solution that has projects in multiple repositories and contribute to them all from a single instance of Visual Studio. To learn more, see the [**Multi-repo support in Visual Studio**](https://devblogs.microsoft.com/visualstudio/multi-repo-support-in-visual-studio/) blog post.
+**New in [17.4](https://devblogs.microsoft.com/visualstudio/visual-studio-2022-17-4/)**: If you've worked with projects hosted on different Git repositories, you might have used external tools or multiple instances of Visual Studio to connect to them. Now, you can work with a single solution that has projects in multiple repositories and contribute to them all from a single instance of Visual Studio. To learn more, see the [**Multi-repo support in Visual Studio**](https://devblogs.microsoft.com/visualstudio/multi-repo-support-in-visual-studio/) and [Multi-repository support released](https://devblogs.microsoft.com/visualstudio/multi-repository-support-released/) blog posts.
 
-**New in [17.3](https://devblogs.microsoft.com/visualstudio/visual-studio-2022-17-3-is-now-available/)**: We recently added line-staging support, also known as [interactive staging](https://git-scm.com/book/en/v2/Git-Tools-Interactive-Staging). Now, you can stage chunks of changes in your files right from the code editor, or split changes across different commits. For more information, see the [**Stage lines of code in Visual Studio**](../version-control/git-line-staging.md) page.
+**New in [17.3](https://devblogs.microsoft.com/visualstudio/visual-studio-2022-17-3-is-now-available/)**: We added line-staging support, also known as [interactive staging](https://git-scm.com/book/en/v2/Git-Tools-Interactive-Staging). Now, you can stage chunks of changes in your files right from the code editor, or split changes across different commits. For more information, see the [**Stage lines of code in Visual Studio**](../version-control/git-line-staging.md) page.
 
 ### IntelliCode improvements
 

docs/python/debugging-mixed-mode-c-cpp-python-in-visual-studio.md

@@ -44,7 +44,9 @@ Mixed-mode debugging features include the following, as explained in this articl
 
 1. When attaching the mixed-mode debugger to an existing process (**Debug** > **Attach to Process**), use the **Select** button to open the **Select Code Type** dialog. Then set the **Debug these code types** option and select **Python (native)** from the list:
 
-    ![Screenshot of choosing the Python (native) code type for mixed-mode debugging.](media/mixed_mode_debugging_attach_type_updated.png)
+
+    ![Screenshot of user selecting the Python (native) code type](media/mixed_mode_debugging_attach_type_updated.png)
+
 
     The code type settings are persistent, so if you want to disable mixed-mode debugging when attaching to a different process later, clear the **Python (native)** code type and apply the **Native** code type.
 
@@ -54,6 +56,8 @@ Mixed-mode debugging features include the following, as explained in this articl
 
 1. To make the source code for standard Python itself available when debugging, visit [https://www.python.org/downloads/source/](https://www.python.org/downloads/source/), download the archive appropriate for your version, and extract it to a folder. You then point Visual Studio to specific files in that folder at whatever point it prompts you.
 
+Using this method for virtual environments, beware that Python for Windows uses a stub *python.exe* for venvs, Visual Studio finds and loads *python.exe* as a subprocess. For Python 3.8 onward - when starting a debug session, since mixed-mode doesn't support multi-process debugging, it ends up debugging just that stub process, instead of the actual application. For attach scenarios, the workaround is to attach to the correct *python.exe*. For launch/F5, you can create your virtual environment using the following command `C:\Python310-64\python.exe -m venv venv --symlinks` (by default, only admins can create symlinks on Windows). For Python versions prior to 3.8, mixed mode debugging should work as expected with venvs. Running in a global environment will not cause these issues for any version of Python.
+
 ## Enable mixed-mode debugging in a C/C++ project
 
 Visual Studio (2017 version 15.5 and later) supports mixed-mode debugging from a C/C++ project (for example, when [embedding Python in another application as described on python.org](https://docs.python.org/3/extending/embedding.html)). To enable mixed-mode debugging, configure the C/C++ project to launch **Python/Native Debugging**:

docs/python/learn-django-in-visual-studio-step-04-full-django-project-template.md

@@ -85,7 +85,7 @@ Nevertheless, to use an existing virtual environment, follow the steps below:
 
 ## Step 4-2: Understand the views and page templates created by the project template
 
-As you observe when you run the project, the app contains three views: Home, About, and Contact. The code for these views is found in the *app/views* folder. Each view function calls `django.shortcuts.render` with the path to a template and a simple dictionary object. For example, the About page is handled by the `about` function:
+As you observe when you run the project, the app contains three views: Home, About, and Contact. The code for these views is found in the *views.py* file. Each view function calls `django.shortcuts.render` with the path to a template and a simple dictionary object. For example, the About page is handled by the `about` function:
 
 ```python
 def about(request):