diff --git a/docs/architecture/modernize-desktop/example-migration.md b/docs/architecture/modernize-desktop/example-migration.md index df4cccf44511f..42f9d4cb2fe27 100644 --- a/docs/architecture/modernize-desktop/example-migration.md +++ b/docs/architecture/modernize-desktop/example-migration.md @@ -68,6 +68,9 @@ Or: try-convert -w "" ``` +> [!NOTE] +> The try-convert tool is run automatically as part of the [.NET Upgrade Assistant tool](https://aka.ms/dotnet-upgrade-assistant). Consider running the full Upgrade Assistant and not just Try Convert. + After the tool attempts the conversion, reload your files in Visual Studio to run and test. There's a possibility that Try Convert won't be able to perform the conversion due to the specifics of your project. In that case, you can refer the below steps. #### Migrate manually diff --git a/docs/architecture/porting-existing-aspnet-apps/additional-migration-resources.md b/docs/architecture/porting-existing-aspnet-apps/additional-migration-resources.md index f6878807cc8e0..e26463a6e4557 100644 --- a/docs/architecture/porting-existing-aspnet-apps/additional-migration-resources.md +++ b/docs/architecture/porting-existing-aspnet-apps/additional-migration-resources.md @@ -54,7 +54,7 @@ You'll find many other ways to connect with .NET developers on the [.NET Communi - [Overview of porting from .NET Framework to .NET Core](../../core/porting/index.md) - [.NET Upgrade Assistant tool](https://aka.ms/dotnet-upgrade-assistant) -- [Migrate from ASP.NET to ASP.NET Core](/aspnet/core/migration/proper-to-2x) +- [Migrate from ASP.NET to ASP.NET Core](../../core/porting/index.md) - [.NET Community Resources](https://dotnet.microsoft.com/platform/community) >[!div class="step-by-step"] diff --git a/docs/architecture/porting-existing-aspnet-apps/incremental-migration-strategies.md b/docs/architecture/porting-existing-aspnet-apps/incremental-migration-strategies.md index 3e007d86af157..36ebf7cd18a54 100644 --- a/docs/architecture/porting-existing-aspnet-apps/incremental-migration-strategies.md +++ b/docs/architecture/porting-existing-aspnet-apps/incremental-migration-strategies.md @@ -15,11 +15,13 @@ Consider the challenge of migrating a large ASP.NET 4.5 app. One approach is to One recent addition to the .NET ecosystem that helps with interoperability between different .NET frameworks is [.NET Standard](https://dotnet.microsoft.com/platform/dotnet-standard). .NET Standard allows libraries to build against the agreed upon set of common APIs, ensuring they can be used in any .NET app. .NET Standard 2.0 is notable because it covers most base class library functionality used by most .NET Framework and .NET Core apps. Unfortunately, the earliest version of .NET with support for .NET Standard 2.0 is .NET Framework 4.6.1, and there are a number of updates in .NET Framework 4.8 that make it a compelling choice for initial upgrades. -One approach to incrementally upgrade a .NET Framework 4.5 system layer-by-layer is to first update its class libraries to .NET Framework 4.8. Then, modify these libraries to be .NET Standard class libraries. Use multi-targeting and conditional compilation, if necessary. This step can be helpful in scenarios where app dependencies require .NET Framework and cannot easily be ported directly to use .NET Standard and .NET Core. Since .NET Framework libraries can be consumed by ASP.NET Core 2.1 apps, the next step is to migrate some or all of the web functionality of the app to ASP.NET Core 2.1 (as described in the [previous chapter](choose-net-core-version.md)). +One approach to incrementally upgrade a .NET Framework 4.5 system layer-by-layer is to first update its class library dependencies to .NET Framework 4.8. Then, modify these libraries to be .NET Standard class libraries. Use multi-targeting and conditional compilation, if necessary. This step can be helpful in scenarios where app dependencies require .NET Framework and cannot easily be ported directly to use .NET Standard and .NET Core. Since .NET Framework libraries can be consumed by ASP.NET Core 2.1 apps, the next step is to migrate some or all of the web functionality of the app to ASP.NET Core 2.1 (as described in the [previous chapter](choose-net-core-version.md)). This is a "bottom up" approach, starting with low level class library dependencies and working up to the web app entry point. Once the app is running on ASP.NET Core 2.1, migrating it to ASP.NET Core 3.1 in isolation is relatively straightforward. The most likely challenge during this step is updating incompatible dependencies to support .NET Core and possibly higher versions of .NET Standard. For apps that don't have problematic dependencies on .NET Framework-only libraries, there's little reason to upgrade to ASP.NET Core 2.1. Porting directly to ASP.NET Core 3.1 makes more sense and requires less effort. -By the time the app is running on .NET Core 3.1, migrating to the current .NET 5.0 release is relatively painless. The process primarily involves updating the target framework of your project files and their associated NuGet package dependencies. While there are several [breaking changes to consider](../../core/compatibility/5.0.md), most apps don't require significant modifications to move from .NET Core 3.1 to .NET 5.0. The primary deciding factor in [choosing between .NET Core 3.1 and .NET 5.0 is likely to be support](choose-net-core-version.md). +By the time the app is running on .NET Core 3.1, migrating to the current .NET 5 release is relatively painless. The process primarily involves updating the target framework of your project files and their associated NuGet package dependencies. While there are several [breaking changes to consider](../../core/compatibility/5.0.md), most apps don't require significant modifications to move from .NET Core 3.1 to .NET 5. The primary deciding factor in [choosing between .NET Core 3.1 and .NET 5 is likely to be support](choose-net-core-version.md). + +Instead of a "bottom up" approach, another alternative is to start with the web app (or even the entire solution) and use an automated tool to assist with the upgrade. The [.NET Upgrade Assistant tool](https://aka.ms/dotnet-upgrade-assistant) can be used to help upgrade .NET Framework apps to .NET Core / .NET 5. It automates many of the common tasks related to upgrading apps, such as modifying project file format, setting appropriate target frameworks, updating NuGet dependencies, and more. Instead of a "bottom up" approach, another alternative is to start with the web app (or even the entire solution) and use an automated tool to assist with the upgrade. The [.NET Upgrade Assistant tool](https://aka.ms/dotnet-upgrade-assistant) can be used to help upgrade .NET Framework apps to .NET Core / .NET 5. It automates many of the common tasks related to upgrading apps, such as modifying project file format, setting appropriate target frameworks, updating NuGet dependencies, and more. diff --git a/docs/architecture/porting-existing-aspnet-apps/migration-considerations.md b/docs/architecture/porting-existing-aspnet-apps/migration-considerations.md index c8276b824dc96..b4e80b3902648 100644 --- a/docs/architecture/porting-existing-aspnet-apps/migration-considerations.md +++ b/docs/architecture/porting-existing-aspnet-apps/migration-considerations.md @@ -11,7 +11,7 @@ The most fundamental question teams must answer when it comes to porting their a ## Is migration to .NET Core appropriate? -Let's start with some of the reasons why you might want to move to .NET Core. There are quite a few, so don't consider this list exhaustive. +Let's start with some of the reasons why you might want to move to .NET Core (or .NET 5). There are quite a few, so don't consider this list exhaustive. ### Cross-platform support