move some more topics into areas

Author: twsouthwick

…ore/migration/claimsprincipal-current.md …to-core/areas/claimsprincipal-current.mdaspnetcore/migration/claimsprincipal-current.md renamed to aspnetcore/migration/fx-to-core/areas/claimsprincipal-current.md aspnetcore/migration/claimsprincipal-current.md renamed to aspnetcore/migration/fx-to-core/areas/claimsprincipal-current.md

@@ -4,17 +4,11 @@ author: ardalis
 description: Learn how to migrate configuration from an ASP.NET MVC project to an ASP.NET Core MVC project.
 ms.author: riande
 ms.date: 10/14/2016
-uid: migration/configuration
+uid: migration/fx-to-core/areas/configuration
 ms.sfi.ropc: t
 ---
 # Migrate configuration to ASP.NET Core
 
-In the previous article, we began to [migrate an ASP.NET MVC project to ASP.NET Core MVC](xref:migration/mvc). In this article, we migrate configuration.
-
-[View or download sample code](https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore/migration/configuration/samples) ([how to download](xref:index#how-to-download-a-sample))
-
-## Setup configuration
-
 ASP.NET Core no longer uses the *Global.asax* and *web.config* files that previous versions of ASP.NET utilized. In the earlier versions of ASP.NET, application startup logic was placed in an `Application_StartUp` method within *Global.asax*. Later, in ASP.NET MVC, a `Startup.cs` file was included in the root of the project; and, it was called when the application started. ASP.NET Core has adopted this approach completely by placing all startup logic in the `Startup.cs` file.
 
 The *web.config* file has also been replaced in ASP.NET Core. Configuration itself can now be configured, as part of the application startup procedure described in `Startup.cs`. Configuration can still utilize XML files, but typically ASP.NET Core projects will place configuration values in a JSON-formatted file, such as `appsettings.json`. ASP.NET Core's configuration system can also easily access environment variables, which can provide a [more secure and robust location](xref:security/app-secrets) for environment-specific values. This is especially true for secrets like connection strings and API keys that shouldn't be checked into source control. See [Configuration](xref:fundamentals/configuration/index) to learn more about configuration in ASP.NET Core.

aspnetcore/migration/configuration.md …ration/fx-to-core/areas/configuration.mdaspnetcore/migration/configuration.md renamed to aspnetcore/migration/fx-to-core/areas/configuration.md aspnetcore/migration/configuration.md renamed to aspnetcore/migration/fx-to-core/areas/configuration.md

@@ -4,17 +4,11 @@ author: ardalis
 description: Learn how to migrate authentication and identity from an ASP.NET MVC project to an ASP.NET Core MVC project.
 ms.author: riande
 ms.date: 10/29/2024
-uid: migration/identity
+uid: migration/fx-to-core/areas/identity
 ---
 <!-- ms.sfi.ropc: t -->
 # Migrate Authentication and Identity to ASP.NET Core
 
-By [Steve Smith](https://ardalis.com/)
-
-In the previous article, we [migrated configuration from an ASP.NET MVC project to ASP.NET Core MVC](xref:migration/configuration). In this article, we migrate the registration, login, and user management features.
-
-## Configure Identity and Membership
-
 In ASP.NET MVC, authentication and identity features are configured using ASP.NET Identity in `Startup.Auth.cs` and `IdentityConfig.cs`, located in the *App_Start* folder. In ASP.NET Core MVC, these features are configured in `Startup.cs`.
 
 Install the following NuGet packages:

aspnetcore/migration/identity.md …e/migration/fx-to-core/areas/identity.mdaspnetcore/migration/identity.md renamed to aspnetcore/migration/fx-to-core/areas/identity.md aspnetcore/migration/identity.md renamed to aspnetcore/migration/fx-to-core/areas/identity.md

@@ -5,7 +5,7 @@ description: Learn how to migrate a web API implementation from ASP.NET 4.x Web
 ms.author: wpickett
 ms.custom: mvc
 ms.date: 01/31/2022
-uid: migration/webapi
+uid: migration/fx-to-core/areas/webapi
 ---
 # Migrate from ASP.NET Web API to ASP.NET Core
 

aspnetcore/migration/webapi.md …ore/migration/fx-to-core/areas/webapi.mdaspnetcore/migration/webapi.md renamed to aspnetcore/migration/fx-to-core/areas/webapi.md aspnetcore/migration/webapi.md renamed to aspnetcore/migration/fx-to-core/areas/webapi.md

@@ -19,8 +19,7 @@ To understand how this approach is helpful in the migration process, see [Increm
 
 ## Set up ASP.NET Core Project
 
-For ASP.NET MVC and Web API apps, see <xref:migration/mvc>.
-For ASP.NET Framework Web Forms apps, see <xref:migration/web_forms>.
+See <xref:migration/fx-to-core/tooling> for help in setting up projects required for incremental migration.
 
 ## Upgrade supporting libraries
 

aspnetcore/migration/fx-to-core/inc/start.md

@@ -4,7 +4,7 @@ description: Learn how to upgrade ASP.NET Framework MVC, Web API, or Web Forms p
 author: rick-anderson
 ms.author: riande
 ms.date: 06/20/2025
-uid: migration/tooling
+uid: migration/fx-to-core/tooling
 ---
 # Use tooling to help migrate ASP.NET Framework to ASP.NET Core
 

aspnetcore/migration/tooling.md …pnetcore/migration/fx-to-core/tooling.mdaspnetcore/migration/tooling.md renamed to aspnetcore/migration/fx-to-core/tooling.md aspnetcore/migration/tooling.md renamed to aspnetcore/migration/fx-to-core/tooling.md

@@ -2125,24 +2125,12 @@ items:
               uid: migration/fx-to-core/inc/ab-testing
             - name: Blazor support with YARP
               uid: migration/fx-to-core/inc/blazor
-          - name: MVC and Web API
-            uid: migration/mvc
-          - name: Web Forms
-            uid: migration/web_forms
-          - name: Web API
-            uid: migration/webapi
-          - name: Configuration
-            uid: migration/configuration
-          - name: Authentication and Identity
-            uid: migration/identity
-          - name: ClaimsPrincipal.Current
-            uid: migration/claimsprincipal-current
+          - name: Tooling
+            uid: migration/fx-to-core
           - name: Technology Areas
             items:
             - name: Overview            
               uid: migration/fx-to-core/areas
-            - name: MVC
-              uid: migration/mvc
             - name: HttpContext
               uid: migration/fx-to-core/areas/http-context
             - name: HTTP Modules
@@ -2151,6 +2139,14 @@ items:
               uid: migration/fx-to-core/areas/http-handlers
             - name: Membership
               uid: migration/fx-to-core/areas/membership
+            - name: Web API
+              uid: migration/fx-to-core/areas/webapi
+            - name: Configuration
+              uid: migration/fx-to-core/areas/configuration
+            - name: Identity
+              uid: migration/fx-to-core/areas/identity
+            - name: ClaimsPrincipal.Current
+              uid: migration/fx-to-core/areas/claimsprincipal-current
   - name: API reference
     href: /dotnet/api/
   - name: Contribute