Merge pull request #10481 from MicrosoftDocs/main638670331677317703sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

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

docs/ide/creating-solutions-and-projects.md

@@ -1,7 +1,7 @@
 ---
 title: "Create projects & solutions"
 description: Create Visual Studio solutions and projects and use them to store artifacts, including source code files, bitmaps, icons, and component and service references.
-ms.date: 10/03/2024
+ms.date: 11/12/2024
 ms.topic: how-to
 f1_keywords:
 - vs.openprojectfromweb
@@ -62,6 +62,21 @@ If you have a file that applies to multiple projects, like a readme file for the
 
 Starting with [version 17.7](/visualstudio/releases/2022/release-notes), you can compare files in Solution Explorer by using the right-click context menu options. For more information, see [The file comparison tool](use-solution-explorer.md#the-file-comparison-tool) in [Learn about Solution Explorer](use-solution-explorer.md).
 
+## Copy files between Visual Studio instances
+
+With Visual Studio version 17.12 and later, you can now copy and paste code files and folders between different Visual Studio instances using the Solution Explorer.
+
+1. Select the desired file or folder in Solution Explorer.
+1. Copy or cut the selected file or folder using **Ctrl+C** or **Ctrl+X**.
+1. Switch to another Visual Studio instance where you want to paste the file or folder.
+1. Paste the file or folder using **Ctrl+V** to include those files or folders in your new solution.
+
+All copied changes will be accurately reflected in the file system.
+
+:::image type="content" source="media/vs-2022/copy-between-visual-studio-instances-using-solution-explorer.gif" alt-text="Copy files or folders between Visual Studio instances using Solution Explorer." lightbox="media/vs-2022/copy-between-visual-studio-instances-using-solution-explorer.gif":::
+
+In addition to copy and paste, you can also drag the files and folders from one instance of Visual Studio to another.
+
 ::: moniker-end
 
 ## Create a .NET project that targets a specific version of the .NET Framework

docs/ide/find-code-changes-and-other-history-with-codelens.md

@@ -75,10 +75,12 @@ You can also view the file-level indicators for an entire file.
 > [!NOTE]
 > File-level indicators are not available for C# and Visual Basic files.
 
-To get more details about a change, right-click the item. Depending on whether you're using TFVC or Git, there are options to compare the versions of the file, view details and track the changeset, get the selected version of the file, and email the author of that change. Some of these details appear in **Team Explorer** if you have it enabled; otherwise, these details appear in **Git Changes**.
+To get more details about a change, right-click the item. Depending on whether you're using TFVC or Git, there are options to compare the versions of the file, view details and track the changeset, get the selected version of the file, and email the author of that change. Some of these details appear in **Team Explorer** if you have it enabled; otherwise, these details appear in **Git Changes** tab, and might also appear on the horizontal scrollbar at the bottom of the editor.
 
 You can also see who changed your code over time, which can help you find patterns in your team's changes and assess their impact.
 
+Starting in Visual Studio 2022 version 17.12 Preview 2, you can show or hide file-level indicators on the editor's horizontal scrollbar. To hide the indicators, open **Tools > Options > Text Editor > Advanced**, and then disable the **Show file level CodeLens indicator** option. This option affects visibility for file types that have the file-level CodeLens control in the bottom editor scrollbar such as XAML, HTML, and CSS, and does not affect files that contain inline CodeLens.
+
 ### Find changes in your current branch
 
 Your team might have multiple branches, for example a main branch and a child development branch, to reduce the risk of breaking stable code. You can find out how many people changed your code and how many changes were made in the main branch by pressing **Alt**+**6**.

docs/ide/media/vs-2022/copy-between-visual-studio-instances-using-solution-explorer.gif

@@ -2,7 +2,7 @@
 title: "What's new in Visual Studio 2022"
 titleSuffix: ""
 description: Discover new features in Visual Studio 2022, including answers to questions and AI consultations while you code with a subscription to GitHub Copilot.
-ms.date: 08/13/2024
+ms.date: 11/12/2024
 helpviewer_keywords:
   - "Visual Studio, what's new"
   - "what's new [Visual Studio]"
@@ -15,7 +15,7 @@ ms.topic: whats-new
 ---
 # What's new in Visual Studio 2022
 
-**Updated for the 17.11 release.** See [full release notes](/visualstudio/releases/2022/release-notes) | View [product roadmap](/visualstudio/productinfo/vs-roadmap/)
+**Updated for the 17.12 release.** See [full release notes](/visualstudio/releases/2022/release-notes) | View [product roadmap](/visualstudio/productinfo/vs-roadmap/)
 
 >[!div class="button"]
 >[Download Visual Studio 2022](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-cta)