move

Author: twsouthwick

aspnetcore/migration/fx-to-core/areas/includes/enable-session.md

@@ -117,10 +117,44 @@ When migrating to built-in ASP.NET Core session:
 * You're not sharing session data with legacy applications
 * You want to eliminate System.Web dependencies completely
 
-## Wrapped ASP.NET Core session state
+## System.Web Adapter Session
 
 [!INCLUDE[](~/migration/fx-to-core/includes/uses-systemweb-adapters.md)]
 
+### Serialization configuration
+
+The <xref:System.Web.SessionState.HttpSessionState> object requires serialization for remote app session state.
+
+In ASP.NET Framework, [BinaryFormatter](/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter) was used to automatically serialize session value contents. In order to serialize these with for use with the System.Web adapters, the serialization must be explicitly configured using `ISessionKeySerializer` implementations.
+
+Out of the box, there is a simple JSON serializer that allows each session key to be registered to a known type using `JsonSessionSerializerOptions`:
+
+* `RegisterKey<T>(string)` - Registers a session key to a known type. This registration is required for correct serialization/deserialization. Missing registrations cause errors and prevent session access.
+
+:::code language="csharp" source="~/migration/fx-to-core/areas/session/samples/serialization/Program.cs" id="snippet_Serialization" :::
+
+If more customization is needed, then `ISessionKeySerializer` can be implemented:
+
+:::code language="csharp" source="~/migration/fx-to-core/areas/session/samples/serialization/Program_Custom.cs" id="snippet_Serialization" :::
+:::code language="csharp" source="~/migration/fx-to-core/areas/session/samples/serialization/Program_Custom.cs" id="snippet_CustomSerializer" :::
+
+> [!NOTE]
+> When using the `AddJsonSessionSerializer` registration pattern, there is no need to call `AddSessionSerializer` as it will automatically be added. If you only want to use a customimplementation, then you must manually add it.
+
+### Enable session
+
+Session support requires explicit activation. Configure it per-route or globally using ASP.NET Core metadata:
+
+* Annotate controllers
+
+:::code language="csharp" source="~/migration/fx-to-core/areas/session/samples/remote/SomeController.cs" id="snippet_Controller" :::
+
+* Enable globally for all endpoints
+
+:::code language="csharp" source="~/migration/fx-to-core/areas/session/samples/remote/Program.cs" id="snippet_RequireSystemWebAdapterSession" :::
+
+## Wrapped ASP.NET Core session state
+
 Choose this approach when your migrated components don't need to share session data with your legacy application.
 
 The `Microsoft.Extensions.DependencyInjection.WrappedSessionExtensions.AddWrappedAspNetCoreSession` extension method adds a wraps ASP.NET Core session to work with the adapters. It uses the same backing store as <xref:Microsoft.AspNetCore.Http.ISession> while providing strongly-typed access.
@@ -133,8 +167,6 @@ Your Framework application requires no changes.
 
 For more information, see the [wrapped session state sample app](https://github.com/dotnet/systemweb-adapters/blob/main/samples/SessionLocal/SessionLocalCore/Program.cs)
 
-[!INCLUDE[](~/migration/fx-to-core/areas/includes/enable-session.md)]
-
 ## Remote app session state
 
 [!INCLUDE[](~/migration/fx-to-core/includes/uses-systemweb-adapters.md)]
@@ -147,26 +179,6 @@ Remote app session enables communication between applications to retrieve and se
 
 Complete the [remote app setup](xref:migration/fx-to-core/inc/remote-app-setup) instructions to connect your ASP.NET Core and ASP.NET Framework applications.
 
-### Serialization configuration
-
-The <xref:System.Web.SessionState.HttpSessionState> object requires serialization for remote app session state.
-
-In ASP.NET Framework, [BinaryFormatter](/dotnet/api/system.runtime.serialization.formatters.binary.binaryformatter) was used to automatically serialize session value contents. In order to serialize these with for use with the System.Web adapters, the serialization must be explicitly configured using `ISessionKeySerializer` implementations.
-
-Out of the box, there is a simple JSON serializer that allows each session key to be registered to a known type using `JsonSessionSerializerOptions`:
-
-* `RegisterKey<T>(string)` - Registers a session key to a known type. This registration is required for correct serialization/deserialization. Missing registrations cause errors and prevent session access.
-
-:::code language="csharp" source="~/migration/fx-to-core/areas/session/samples/serialization/Program.cs" id="snippet_Serialization" :::
-
-If more customization is needed, then `ISessionKeySerializer` can be implemented:
-
-:::code language="csharp" source="~/migration/fx-to-core/areas/session/samples/serialization/Program_Custom.cs" id="snippet_Serialization" :::
-:::code language="csharp" source="~/migration/fx-to-core/areas/session/samples/serialization/Program_Custom.cs" id="snippet_CustomSerializer" :::
-
-> [!NOTE]
-> When using the `AddJsonSessionSerializer` registration pattern, there is no need to call `AddSessionSerializer` as it will automatically be added. If you only want to use a customimplementation, then you must manually add it.
-
 ### Application configuration
 
 :::zone pivot="manual"
@@ -200,8 +212,6 @@ var coreApp = builder.AddProject<Projects.CoreApplication>("core")
 
 :::zone-end
 
-[!INCLUDE[](~/migration/fx-to-core/areas/includes/enable-session.md)]
-
 ### Communication protocol
 
 #### Readonly sessions