Merge pull request #10378 from MicrosoftDocs/main638606379678668245sync_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/msbuild/how-to-use-project-sdk.md

@@ -38,7 +38,7 @@ During evaluation of the project, MSBuild adds implicit imports at the top and b
 </Project>
 ```
 
-There are many SDKs distributed by Microsoft, referenced in the previous example by its moniker `Microsoft.NET.Sdk`. The ones associated with .NET Core and .NET 5 and later are listed at [.NET Project SDK overview](/dotnet/core/project-sdk/overview).
+There are many SDKs distributed by Microsoft. The project SDK referenced in the previous example has the moniker `Microsoft.NET.Sdk`. The project SDKs associated with .NET Core and .NET 5 and later are listed at [.NET Project SDK overview](/dotnet/core/project-sdk/overview).
 
 ## Reference a project SDK
 
@@ -88,16 +88,16 @@ The `Version` attribute isn't required.
 </Project>
 ```
 
-Explicitly including the imports in your project allows you full control over the order.
+When you explicitly include the imports in your project, you have full control over the order.
 
 When using the `<Import/>` element, you can specify an optional `Version` attribute as well. For example, you can specify `<Import Project="Sdk.props" Sdk="My.Custom.Sdk" Version="1.2.3" />`.
 
 > [!WARNING]
-> If you are changing project to use `<Import/>` elements, make sure you add both `.props` and `.targets` imports and that you remove the SDK from the `<Project/>` element and `<Sdk/>` elements. Failure to do so will result in doubled imports and an [`MSB4011`](./errors/msb4011.md) warning.
+> If you change your project to use `<Import/>` elements, make sure you add both `.props` and `.targets` imports, and that you remove the SDK from the `<Project/>` element and `<Sdk/>` elements. Failure to do so will result in doubled imports and an [`MSB4011`](./errors/msb4011.md) warning.
 
 ## How project SDKs are resolved
 
-When evaluating the import, MSBuild dynamically resolves the path to the project SDK based on the name and version you specified.  MSBuild also has a list of registered SDK resolvers, which are plug-ins that locate project SDKs on your machine. These plug-ins include:
+When evaluating the import, MSBuild dynamically resolves the path to the project SDK based on the name and version you specified. MSBuild also has a list of registered SDK resolvers, which are plug-ins that locate project SDKs on your machine. These plug-ins include:
 
 - A NuGet-based resolver that queries your configured package feeds for NuGet packages that match the ID and version of the SDK you specified.
 
@@ -127,4 +127,4 @@ Only one version of each project SDK can be used during a build. If you referenc
 - [MSBuild concepts](../msbuild/msbuild-concepts.md)
 - [Customize your build](../msbuild/customize-your-build.md)
 - [Packages, metadata, and frameworks](/dotnet/core/packages)
-- [Additions to the csproj format for .NET Core](/dotnet/core/tools/csproj)
+- [MSBuild reference for .NET SDK projects](/dotnet/core/project-sdk/msbuild-props)

docs/xaml-tools/creating-a-ui-by-using-blend-for-visual-studio.md

@@ -2,7 +2,7 @@
 title: Blend for Visual Studio feature tour
 titleSuffix: ''
 description: Explore the features and workspace UI in Blend for Visual Studio, a component for designing XAML-based Windows and Web applications.
-ms.date: 07/31/2019
+ms.date: 07/31/2024
 ms.topic: overview
 f1_keywords:
 - Blend.Start.Dev12
@@ -11,6 +11,7 @@ ms.author: maleger
 manager: mijacobs
 ms.subservice: xaml-tools
 ---
+
 # Blend for Visual Studio overview
 
 Blend for Visual Studio helps you design XAML-based Windows and Web applications. It provides the same basic XAML design experience as Visual Studio and adds visual designers for advanced tasks such as animations and behaviors. For a comparison between Blend and Visual Studio, see [Design XAML in Visual Studio and Blend for Visual Studio](../xaml-tools/designing-xaml-in-visual-studio.md).

docs/xaml-tools/creating-a-ui-by-using-xaml-designer-in-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: Create UIs with Visual Studio XAML Designer
 description: Explore XAML Designer workspace UI and features in Blend for Visual Studio that provides a visual interface to help you design XAML-based apps.
-ms.date: 07/04/2023
+ms.date: 08/30/2024
 ms.topic: conceptual
 f1_keywords:
 - VS.XamlDesigner
@@ -21,10 +21,12 @@ The XAML Designer in Visual Studio and Blend for Visual Studio provides a visual
 For advanced users, you can even [customize the XAML Designer](https://github.com/microsoft/xaml-designer-extensibility/blob/master/documents/xaml-designer-extensibility-migration.md).
 
 > [!NOTE]
-> Xamarin.Forms does not support a XAML designer. To view your Xamarin.Forms XAML UIs and edit them while the app is running, use XAML Hot Reload for Xamarin.Forms. For more information, see the [XAML Hot Reload for Xamarin.Forms (Preview)](/xamarin/xamarin-forms/xaml/hot-reload/) page.
+> WinUI 3 / .NET MAUI XAML designer is not supported in Visual Studio 2022. To view your WinUI 3 / .NET MAUI XAML UIs and edit them while the app is running, use XAML Hot Reload for WinUI 3 / .NET MAUI. For more information, see the [XAML Hot Reload](../xaml-tools/xaml-hot-reload.md) page.
 
+::: moniker range="vs-2019"
 > [!NOTE]
-> WinUI 3 / .NET MAUI XAML designer is not supported in Visual Studio 2022. To view your WinUI 3 / .NET MAUI XAML UIs and edit them while the app is running, use XAML Hot Reload for WinUI 3 / .NET MAUI. For more information, see the [XAML Hot Reload](../xaml-tools/xaml-hot-reload.md) page.
+> Xamarin.Forms does not support a XAML designer. To view your Xamarin.Forms XAML UIs and edit them while the app is running, use XAML Hot Reload for Xamarin.Forms. For more information, see the [XAML Hot Reload for Xamarin.Forms (Preview)](/xamarin/xamarin-forms/xaml/hot-reload/) page.
+::: moniker-end
 
 ## XAML Designer workspace
 

docs/xaml-tools/xaml-hot-reload.md

@@ -1,7 +1,7 @@
 ---
 title: "XAML Hot Reload for WPF and UWP apps"
 description: Modify XAML code in running .NET MAUI, WinUI 3, Windows Presentation Foundation (WPF), or Universal Windows Platform (UWP) apps with edit and continue features in XAML Hot Reload.
-ms.date: 02/25/2022
+ms.date: 08/27/2024
 ms.topic: conceptual
 helpviewer_keywords:
   - "xaml edit and continue"
@@ -39,10 +39,10 @@ XAML Hot Reload is especially helpful in these scenarios:
 
 |Supported Application Types|Operating System and Tools|
 |---|---|
-|.NET MAUI|.NET6+|
+|.NET MAUI|.NET 6+|
 |Windows Presentation Foundation (WPF) |.NET Framework 4.6+, .NET Core, and .NET 5+</br>Windows 7 and later |
 |Universal Windows apps (UWP)|Windows 10 and later, with the [Windows 10 SDK](https://developer.microsoft.com/windows/downloads/windows-sdk/) 14393+ and later|
-|WinUI 3)|Windows 10, version 1809 and later, with the Windows App SDK|
+|WinUI 3|Windows 10, version 1809 and later, with the Windows App SDK|
 
 If you're using **.NET MAUI**, see [XAML Hot Reload for .NET MAUI](/dotnet/maui/xaml/hot-reload) for more details.