move inc folder

Author: twsouthwick

.openpublishing.redirection.json

@@ -976,7 +976,7 @@
             "redirect_document_id": false
         },
         {
-            "source_path": "aspnetcore/migration/inc/http-modules.md",
+            "source_path": "aspnetcore/migration/fx-to-core/inc/http-modules.md",
             "redirect_url": "/aspnet/core/migration/fx-to-core/areas/http-modules",
             "redirect_document_id": false
         },

aspnetcore/migration/70-80.md

@@ -483,7 +483,7 @@ Updated configuration guidance appears in the following locations:
 
 ### Drop Blazor Server with Yarp routing workaround
 
-If you previously followed the guidance in <xref:migration/inc/blazor?view=aspnetcore-7.0&preserve-view=true> for migrating a Blazor Server app with Yarp to .NET 6 or .NET 7, you can reverse the workaround steps that you took when following the article's guidance. Routing and deep linking for Blazor Server with Yarp work correctly in .NET 8.
+If you previously followed the guidance in <xref:migration/fx-to-core/inc/blazor?view=aspnetcore-7.0&preserve-view=true> for migrating a Blazor Server app with Yarp to .NET 6 or .NET 7, you can reverse the workaround steps that you took when following the article's guidance. Routing and deep linking for Blazor Server with Yarp work correctly in .NET 8.
 
 ### Migrate `CascadingValue` components in layout components
 

aspnetcore/migration/inc/abtesting.md renamed to aspnetcore/migration/fx-to-core/inc/abtesting.md

@@ -6,14 +6,14 @@ ms.author: tasou
 monikerRange: '>= aspnetcore-6.0'
 ms.date: 3/1/2023
 ms.topic: article
-uid: migration/inc/ab-testing
+uid: migration/fx-to-core/inc/ab-testing
 ---
 
 # A/B Testing endpoints during migration
 
 During incremental migration, new endpoints are brought over to a [YARP](https://dotnet.github.io/yarp/) enabled ASP.NET Core app. With the default setup, these endpoints are automatically served for all requests once deployed. In order to test these endpoints, or be able to turn them off if needed, additional setup is needed.
 
-This document describes how to setup a conditional endpoint selection system to enable A/B testing during incremental migration. It assumes a setup as described in [incremental migration overview](xref:migration/inc/overview) as a starting point.
+This document describes how to setup a conditional endpoint selection system to enable A/B testing during incremental migration. It assumes a setup as described in [incremental migration overview](xref:migration/fx-to-core/inc/overview) as a starting point.
 
 ## Conditional endpoint selection
 

aspnetcore/migration/inc/blazor.md renamed to aspnetcore/migration/fx-to-core/inc/blazor.md

@@ -6,7 +6,7 @@ monikerRange: '>= aspnetcore-6.0 < aspnetcore-8.0'
 ms.author: tasou
 ms.custom: "mvc"
 ms.date: 03/01/2023
-uid: migration/inc/blazor
+uid: migration/fx-to-core/inc/blazor
 ---
 # Enable ASP.NET Core Blazor Server support with Yarp in incremental migration
 

aspnetcore/migration/inc/includes/mermaid.md renamed to aspnetcore/migration/fx-to-core/inc/includes/mermaid.md

@@ -6,7 +6,7 @@ ms.author: riande
 monikerRange: '>= aspnetcore-6.0'
 ms.date: 11/9/2022
 ms.topic: article
-uid: migration/inc/overview
+uid: migration/fx-to-core/inc/overview
 ---
 
 <!-- see mermaid.txt to change diagrams -->
@@ -19,24 +19,24 @@ One of the larger challenges is the pervasive use of <xref:System.Web.HttpContex
 
 A complete migration may take considerable effort depending on the size of the app, dependencies, and non-portable APIs used. In order to keep deploying an app to production while working on updating, the best pattern is to follow is the [Strangler Fig pattern](/azure/architecture/patterns/strangler-fig). The *Strangler Fig pattern* allows for continual development on the old system with an incremental approach to replacing specific pieces of functionality with new services. This document describes how to apply the Strangler Fig pattern to an ASP.NET app updating towards ASP.NET Core.
 
-If you'd like to skip this overview article and get started, see [Get started](xref:migration/inc/start).
+If you'd like to skip this overview article and get started, see [Get started](xref:migration/fx-to-core/inc/start).
 
 ## App migration to ASP.NET Core
 
 Before starting the migration, the app targets ASP.NET Framework and runs on Windows with its supporting libraries:
 
-![Before starting the migration](~/migration/inc/overview/static/1.png)
+![Before starting the migration](~/migration/fx-to-core/inc/overview/static/1.png)
 
 Migration starts by introducing a new app based on ASP.NET Core that becomes the entry point. Incoming requests go to the ASP.NET Core app, which either handles the request or proxies the request to the .NET Framework app via [YARP](https://dotnet.github.io/yarp/). At first, the majority of code providing responses is in the .NET Framework app, but the ASP.NET Core app is now set up to start migrating routes:
 
-![start updating routes](~/migration/inc/overview/static/nop.png)
+![start updating routes](~/migration/fx-to-core/inc/overview/static/nop.png)
 
 To migrate business logic that relies on `HttpContext`, the libraries need to be built with `Microsoft.AspNetCore.SystemWebAdapters`. Building the libraries with `SystemWebAdapters` allows:
 
 * The libraries to be built against .NET Framework, .NET Core, or .NET Standard 2.0.
 * Ensures that the libraries are using APIs that are available on both ASP.NET Framework and ASP.NET Core.
 
-![Microsoft.AspNetCore.SystemWebAdapters](~/migration/inc/overview/static/sys_adapt.png)
+![Microsoft.AspNetCore.SystemWebAdapters](~/migration/fx-to-core/inc/overview/static/sys_adapt.png)
 
 Once the ASP.NET Core app using YARP is set up, you can start updating routes from ASP.NET Framework to ASP.NET Core. For example, WebAPI or MVC controller action methods,handlers, or some other implementation of a route. If the route is available in the ASP.NET Core app, it's matched and served.
 
@@ -48,14 +48,14 @@ During the migration process, additional services and infrastructure are identif
 
 Eventually, the ASP.NET Core app handles more of the routes than the .NET Framework app:
 
-![the ASP.NET Core app handles more of the routes](~/migration/inc/overview/static/sys_adapt.png)
+![the ASP.NET Core app handles more of the routes](~/migration/fx-to-core/inc/overview/static/sys_adapt.png)
 
 Once the ASP.NET Framework app is no longer needed and deleted:
 
 * The app is running on the ASP.NET Core app stack, but is still using the adapters.
 * The remaining migration work is removing the use of adapters.
 
-![final pic](~/migration/inc/overview/static/final.png)
+![final pic](~/migration/fx-to-core/inc/overview/static/final.png)
 
 The Visual Studio extension [.NET Upgrade Assistant](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.upgradeassistant) can help upgrade ASP.NET Framework web apps to ASP.NET Core. For more information see the blog post [Upgrading your .NET projects with Visual Studio](https://devblogs.microsoft.com/dotnet/upgrade-assistant-now-in-visual-studio/).
 
@@ -68,12 +68,12 @@ The `Microsoft.AspNetCore.SystemWebAdapters` namespace is a collection of runtim
 * `Microsoft.AspNetCore.SystemWebAdapters.CoreServices`: This package only targets .NET 6+ and is intended to provide services to ASP.NET Core applications to configure behavior of `System.Web` APIs as well as opting into any behaviors for incremental migration. This is generally not expected to be referenced from libraries, but rather from the applications themselves.
 * `Microsoft.AspNetCore.SystemWebAdapters.Abstractions`: This package is a supporting package that provides abstractions for services used by both the ASP.NET Core and ASP.NET Framework application such as session state serialization.
 
-For examples of scenarios where this is useful, see [the adapters article](xref:migration/inc/adapters).
+For examples of scenarios where this is useful, see [the adapters article](xref:migration/fx-to-core/inc/adapters).
 
-For guidance around usage, see the [usage guidance article](xref:migration/inc/usage_guidance).
+For guidance around usage, see the [usage guidance article](xref:migration/fx-to-core/inc/usage_guidance).
 
 ## Additional Resources
 
 * [Example migration of eShop to ASP.NET Core](/dotnet/architecture/porting-existing-aspnet-apps/example-migration-eshop)
 * [Video:Tooling for Incremental ASP.NET Core Migrations](https://www.youtube.com/watch?v=P96l0pDNVpM)
-* <xref:migration/inc/unit-testing>
+* <xref:migration/fx-to-core/inc/unit-testing>