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

Learn Build Service GitHub App · Learn Build Service GitHub App · commit 4f084ed1d152 · 2025-02-04T01:05:05.000Z
diff --git a/docs/azure/overview.md b/docs/azure/overview.md
@@ -56,6 +56,14 @@ What are you deploying?
 
 If you need help configuring CI/CD for a GitHub repo for the first time, Visual Studio can help you get started with GitHub Action starter workflows. Learn more at [Deploy your application to Azure using GitHub Actions workflows created by Visual Studio](azure-deployment-using-github-actions.md). Read more about setting up CI/CD for deployment to Azure at [Continuous deployment to Azure App Service](/azure/app-service/deploy-continuous-deployment?tabs=github).
 
+## .NET Aspire
+
+[.NET Aspire](/dotnet/aspire) provides infrastructure for orchestrating services and components of observable, cloud-based apps. *Observable apps* are those that are set up to be thoroughly monitored in real-time while executing. .NET Aspire is particularly relevant during development time as a means of organizing and coordinating multiple services, databases, and other dependencies.
+
+Visual Studio 17.9 and later, with the **ASP.NET and web development** and **Azure development** workloads installed, includes the [.NET Aspire SDK](/dotnet/aspire/fundamentals/dotnet-aspire-sdk) and provides [project templates](/dotnet/aspire/fundamentals/aspire-sdk-templates?pivots=visual-studio) for .NET Aspire.
+
+ASP.NET Core projects include an option to enlist in Aspire orchestration at project creation time, and a context menu item, **Add** > **NET Aspire Orchestrator Support** in Solution Explorer that you can use to enlist a project in Aspire orchestration. These actions add Aspire orchestration projects (AppHost and ServiceDefaults) to the solution (unless already present). In Visual Studio 17.13 and later, this functionality is also supported for Azure Functions projects. For more detailed information, see [.NET Aspire tooling](/dotnet/aspire/fundamentals/setup-tooling?tabs=windows&pivots=visual-studio).
+
 ## Debug in Azure using Visual Studio
 
 You can use Visual Studio debug your application while it's running in Azure, so that you can identify and reproduce problems in an environment that is as close as possible to a production environment. For web apps hosted in Azure App Service, see [Remote debug ASP.NET Core on Azure App Service](../debugger/remote-debugging-azure-app-service.md). For Azure Functions, see [Develop Azure Functions with Visual Studio - Remote debugging](/azure/azure-functions/functions-develop-vs#remote-debugging?tabs=isolated-process).
diff --git a/docs/data-tools/create-a-sql-database-by-using-a-designer.md b/docs/data-tools/create-a-sql-database-by-using-a-designer.md
@@ -1,7 +1,7 @@
 ---
 title: Create database, add tables in .NET Framework apps
 description: Create a database with tables and foreign keys in a .NET Framework application by using Table Designer in Visual Studio.
-ms.date: 02/01/2024
+ms.date: 02/03/2025
 ms.topic: conceptual
 helpviewer_keywords:
 - database tables, creating
diff --git a/docs/designers/disable-dpi-awareness.md b/docs/designers/disable-dpi-awareness.md
@@ -1,7 +1,7 @@
 ---
 title: Fix DPI display issues in Windows Form Designer
 description: Fix DPI display problems in Windows Forms Designer in Visual Studio to correct scaling and rendering on HDPI (high dots per inch) monitors.
-ms.date: 02/08/2024
+ms.date: 02/03/2025
 author: ghogen
 ms.author: ghogen
 manager: mijacobs
diff --git a/docs/get-started/csharp/index.yml b/docs/get-started/csharp/index.yml
@@ -8,7 +8,7 @@ metadata:
   description: Explore how to create different C# applications by using Visual Studio, including console, web, Windows Forms, and Windows Desktop apps, and find coding resources.
   ms.custom: vs-acquisition
   ms.topic: landing-page
-  ms.date: 2/13/2024
+  ms.date: 2/3/2025
   author: ghogen
   ms.author: ghogen  
   manager: mijacobs
@@ -51,6 +51,8 @@ landingContent:
             url: tutorial-wpf.md
           - text: Create a Windows Forms app
             url: ../../ide/create-csharp-winform-visual-studio.md
+          - text: Create a mobile app with .NET MAUI
+            url: /dotnet/maui/get-started/first-app?tabs=vswin
           - text: Learn about the C# language
             url: /dotnet/csharp/tutorials/intro-to-csharp/
           - text: Windows Forms Match Game
diff --git a/docs/ide/class-designer/designing-and-viewing-classes-and-types.md b/docs/ide/class-designer/designing-and-viewing-classes-and-types.md
@@ -1,7 +1,7 @@
 ---
 title: Design, visualize, & refactor with Class Designer
 description: Design, visualize, and refactor classes, other types, and their relationships in your code with Class Designer in Visual Studio.
-ms.date: 01/07/2025
+ms.date: 02/03/2025
 ms.topic: conceptual
 f1_keywords:
 - vs.classdesigner.diagram
@@ -285,7 +285,7 @@ You can resize a comment shape but you can't change other aspects of its appeara
 
 ## Use the mouse and keyboard shortcuts in the Class Diagram and Class Details window
 
-You can use the keyboard in addition to the mouse to perform navigational actions in **Class Designer** and in the **Class Details** window.
+You can use the keyboard in addition to the mouse (or other pointing device) to perform navigational actions in **Class Designer** and in the **Class Details** window.
 
 ### Use the mouse in Class Designer
 
diff --git a/docs/ide/compiling-and-building-in-visual-studio.md b/docs/ide/compiling-and-building-in-visual-studio.md
@@ -1,7 +1,7 @@
 ---
 title: Use different build methods to build apps
 description: Use the Visual Studio IDE build method, the MSBuild command-line tools build method, or Azure Pipelines build method to build an application.
-ms.date: 1/7/2025
+ms.date: 2/3/2025
 ms.subservice: compile-build
 ms.topic: conceptual
 helpviewer_keywords:
diff --git a/docs/ide/creating-project-and-item-templates.md b/docs/ide/creating-project-and-item-templates.md
@@ -1,7 +1,7 @@
 ---
 title: Templates for projects and files
 description: Explore how project and item templates in Visual Studio provide reusable stubs that give users some basic code and structure.
-ms.date: 1/07/2025
+ms.date: 2/3/2025
 ms.topic: conceptual
 helpviewer_keywords:
 - templates [Visual Studio], project
diff --git a/docs/ide/how-to-specify-build-events-csharp.md b/docs/ide/how-to-specify-build-events-csharp.md
@@ -1,7 +1,7 @@
 ---
 title: 'Specify build events (C#)'
 description: Use build events in Visual Studio to specify commands that run before the build starts or after the build finishes for C# programs.
-ms.date: 02/01/2024
+ms.date: 02/03/2025
 ms.subservice: compile-build
 ms.topic: how-to
 helpviewer_keywords:
@@ -121,7 +121,7 @@ For guidance on the commands you can use in batch files, see [Windows commands](
 
 Commonly available "macros" (actually MSBuild properties) are listed at [MSBuild common properties](../msbuild/common-msbuild-project-properties.md). For .NET SDK projects (.NET Core or .NET 5 and later), additional properties are listed at [MSBuild properties for Microsoft.NET.Sdk](/dotnet/core/project-sdk/msbuild-props).
 
-In your scripts for build events, you might want to reference the values of some project-level variables such as the name of the project or the location of the output folder. In prior versions of Visual Studio, these were called *macros*. The equivalent to macros in recent versions of Visual Studio are MSBuild properties. MSBuild is the build engine that Visual Studio uses to process your project file when it performs a build. A build event in the IDE results in an MSBuild [target](../msbuild/msbuild-targets.md) in the project file. You can use any MSBuild property that is available in the target in your project file (for example, `$(OutDir)` or `$(Configuration)`) . The MSBuild properties that are available to you in these events depend on the files implicitly or explicitly imported in a project file, such `.props` and `.targets` files, and properties set in your project file, such as in `PropertyGroup` elements. Be careful to use the exact spelling of each property. No error is reported if you misspell a property; instead, an undefined property evaluates to an empty string.
+In your scripts for build events, you might want to reference the values of some project-level variables such as the name of the project or the location of the output folder. In prior versions of Visual Studio, these were called *macros*. The equivalent to macros in recent versions of Visual Studio are MSBuild properties. MSBuild is the build engine that Visual Studio uses to process your project file when it performs a build. A build event in the IDE results in an MSBuild [target](../msbuild/msbuild-targets.md) in the project file. You can use any MSBuild property that is available in the target in your project file (for example, `$(OutDir)` or `$(Configuration)`). The MSBuild properties that are available to you in these events depend on the files implicitly or explicitly imported in a project file, such `.props` and `.targets` files, and properties set in your project file, such as in `PropertyGroup` elements. Be careful to use the exact spelling of each property. No error is reported if you misspell a property; instead, an undefined property evaluates to an empty string.
 
 For example, suppose you specify a pre-build event as follows:
 
diff --git a/docs/msbuild/customize-by-directory.md b/docs/msbuild/customize-by-directory.md
@@ -1,7 +1,7 @@
 ---
 title: Customize your build by folder or solution
 description: Explore the special imports Directory.Build.props and Directory.Build.targets that you can use to customize the build system in Visual Studio.
-ms.date: 02/01/2024
+ms.date: 02/03/2025
 ms.topic: how-to
 helpviewer_keywords:
 - MSBuild, transforms
@@ -131,7 +131,7 @@ The Boolean properties `$(ImportDirectoryBuildProps)` and `$(ImportDirectoryBuil
 
 ## Example
 
-This example shows the use the preprocessed output to determine where to set a property.
+This example shows the use of the preprocessed output to determine where to set a property.
 
 To help you analyze the usage of a particular property you want to set, you can run MSBuild with the `/preprocess` or `/pp` argument. The output text is the result of all the imports, including the system imports like *Microsoft.Common.props* that are implicitly imported, and any of your own imports. With this output, you can see where your property needs to be set relative to where its value is used.
 
diff --git a/docs/msbuild/customize-your-build.md b/docs/msbuild/customize-your-build.md
@@ -1,7 +1,7 @@
 ---
 title: Customize your build with extensibility hooks
 description: Customize your build with several extensibility hooks that you can use to modify MSBuild projects that use the standard build process. 
-ms.date: 02/13/2024
+ms.date: 02/03/2025
 ms.topic: how-to
 helpviewer_keywords:
 - MSBuild, transforms
diff --git a/docs/msbuild/net-sdk-multitargeting.md b/docs/msbuild/net-sdk-multitargeting.md
@@ -0,0 +1,135 @@
+---
+title: .NET SDK Multitargeting Overview
+description: Use MSBuild to compile an application to run on any one of several versions of .NET.
+ms.date: 1/9/2025
+ms.topic: how-to
+author: ghogen
+ms.author: ghogen
+manager: mijacobs
+ms.subservice: msbuild
+---
+# Targeting multiple .NET versions in a build
+
+Targeting multiple .NET frameworks in a build allows you to ensure that your application or library is available for different versions or editions of .NET.
+
+Multitargeting for .NET Core and .NET 5 and later projects is significantly different from and more advanced than multitargeting for .NET Framework projects. See [Comparison between .NET Framework and .NET Core multitargeting](#comparison-between-net-framework-and-net-core-multitargeting).
+
+## Set up .NET multitargeting
+
+1. Create a new .NET Standard class library either in Visual Studio or using the `dotnet new classlib` command.
+
+2. Edit the project file. Edit the `.csproj` file to support multiple target frameworks. Change the `<TargetFramework>` element to `<TargetFrameworks>` and list the frameworks you want to target.
+
+   ```xml
+   <Project Sdk="Microsoft.NET.Sdk">
+   <PropertyGroup>
+       <TargetFrameworks>netstandard2.0;net45;netcoreapp3.1;net5.0</TargetFrameworks>
+   </PropertyGroup>
+   </Project>
+   ```
+
+3. Use conditional compilation symbols to separate code that is specific to a particular version.
+
+    ```csharp
+    public string GetFramework()
+    {
+    #if NET45
+        return ".NET Framework 4.5";
+    #elif NETSTANDARD2_0
+        return ".NET Standard 2.0";
+    #elif NETCOREAPP3_1
+        return ".NET Core 3.1";
+    #elif NET5_0
+        return ".NET 5.0";
+    #else
+        return "Unknown Framework";
+    #endif
+    }
+    ```
+
+4. Build and pack. Use the `dotnet pack` or `MSBuild.exe /t:pack` command to create the package. This will generate a `.nupkg` file that targets all specified frameworks.
+
+   ```sh
+   MSBuild.exe /t:pack MyProject.csproj
+   ```
+
+## Handle dependencies
+
+When targeting multiple framework versions, you might need to handle dependencies differently for each version. Use conditional `ItemGroup` elements in your project file to specify framework-specific dependencies.
+
+```xml
+<ItemGroup Condition="'$(TargetFramework)' == 'net45'">
+<PackageReference Include="SomePackage" Version="1.0.0" />
+</ItemGroup>
+<ItemGroup Condition="'$(TargetFramework)' == 'netstandard2.0'">
+<PackageReference Include="SomeOtherPackage" Version="2.0.0" />
+</ItemGroup>
+```
+
+Handling version-specific dependencies in a .NET project involves using conditional `PackageReference` elements in your project file. This allows you to specify different versions of a package for different target frameworks. Here's how you can do it:
+
+### Add version-specific dependencies
+
+1. **Edit the Project File**: Open your `.csproj` file and add conditional `PackageReference` elements inside an `ItemGroup` element. This way, you can specify different versions of a package based on the target framework.
+
+   ```xml
+    <Project Sdk="Microsoft.NET.Sdk">
+    <PropertyGroup>
+        <TargetFrameworks>net45;netstandard2.0;netcoreapp3.1;net5.0</TargetFrameworks>
+    </PropertyGroup>
+    <ItemGroup Condition="'$(TargetFramework)' == 'net45'">
+        <PackageReference Include="SomePackage" Version="1.0.0" />
+    </ItemGroup>
+    <ItemGroup Condition="'$(TargetFramework)' == 'netstandard2.0'">
+        <PackageReference Include="SomePackage" Version="2.0.0" />
+    </ItemGroup>
+    <ItemGroup Condition="'$(TargetFramework)' == 'netcoreapp3.1'">
+        <PackageReference Include="SomePackage" Version="3.0.0" />
+    </ItemGroup>
+    <ItemGroup Condition="'$(TargetFramework)' == 'net5.0'">
+        <PackageReference Include="SomePackage" Version="4.0.0" />
+    </ItemGroup>
+    </Project>
+   ```
+
+2. **Use the CLI**: You can also add dependencies using the .NET CLI. For example, to add a dependency for a specific target framework, you can use the following command:
+
+   ```sh
+    dotnet add package SomePackage --version 1.0.0 --framework net45
+   ```
+
+### Manage transitive dependencies
+
+Transitive dependencies are dependencies of your dependencies. It's important to review and manage these to avoid conflicts and ensure compatibility. You can use the `dotnet list package` command to see all the dependencies and their versions.
+
+```sh
+dotnet list package
+```
+
+### Handle diamond dependencies
+
+Diamond dependencies occur when multiple versions of a package are present in the dependency tree. NuGet resolves these by selecting the lowest applicable version. To avoid issues, you can specify version ranges or use binding redirects in .NET Framework projects.
+
+```xml
+<PackageReference Include="ExamplePackage" Version="[1.0,2.0)" />
+```
+
+By following these practices, you can effectively manage version-specific dependencies in your .NET projects, ensuring compatibility and stability across different target frameworks. See [Manage package dependencies in .NET applications](/dotnet/core/tools/dependencies), [Dependencies](/dotnet/standard/library-guidance/dependencies), and [How NuGet resolves package dependencies](/nuget/concepts/dependency-resolution).
+
+## Comparison Between .NET Framework and .NET Core Multitargeting
+
+Multitargeting for .NET Core (and .NET 5 and later) is very different and more powerful than [multitargeting for .NET Framework projects](msbuild-multitargeting-overview.md).
+
+### .NET Framework
+- **Limited Multitargeting**: .NET Framework supports multitargeting, but it is more limited compared to .NET Core. It can target different versions of the .NET Framework, but not multiple frameworks simultaneously. See [MSBuild multitargeting](msbuild-multitargeting-overview.md).
+- **Older Toolset**: Uses an older type of multitargeting with MSBuild, where a project can target only one framework and one platform at a time.
+
+### .NET Core
+- **Advanced Multitargeting**: .NET Core supports advanced multitargeting, allowing you to target multiple frameworks simultaneously using the `<TargetFrameworks>` property in the project file. See [Target frameworks](/dotnet/targetframeworks).
+- **Modern Toolset**: Uses a newer type of multitargeting with MSBuild, where multiple builds occur for each target framework listed.
+
+## Related content
+
+- [Specify the targeted .NET Frameworks - Visual Studio](../ide/visual-studio-multi-targeting-overview.md)
+
+[!INCLUDE[AI generated](../includes/ai-generated-attribution.md)]
diff --git a/docs/msbuild/toc.yml b/docs/msbuild/toc.yml
@@ -146,7 +146,9 @@ items:
         href: fix-intermittent-build-failures.md
     - name: Multitargeting
       items:
-      - name: MSBuild multitargeting overview
+      - name: .NET SDK multitargeting
+        href: net-sdk-multitargeting.md
+      - name: .NET Framework multitargeting
         href: msbuild-multitargeting-overview.md
       - name: Toolset (ToolsVersion)
         items:
