Run any Skill in Manus with one click

ef6-migration-policy

Stars2

Forks4

UpdatedApril 28, 2026 at 22:24

EF6 to EF Core migration policy for .NET Framework to modern .NET upgrades. Use when: assessing EF6 usage, planning package compatibility, multitargeting projects with Entity Framework 6. EF Core is NOT supported on .NET Framework — EF6 packages must be retained during framework-to-modern-dotnet migration and only migrated to EF Core as a separate post-migration effort.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

twsouthwick

twsouthwick/fx2dotnet

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	ef6-migration-policy
description	EF6 to EF Core migration policy for .NET Framework to modern .NET upgrades. Use when: assessing EF6 usage, planning package compatibility, multitargeting projects with Entity Framework 6. EF Core is NOT supported on .NET Framework — EF6 packages must be retained during framework-to-modern-dotnet migration and only migrated to EF Core as a separate post-migration effort.

EF6 Migration Policy

Policy

Entity Framework 6 (EF6) must NOT be migrated to Entity Framework Core (EF Core) during a .NET Framework to modern .NET migration. EF Core does not support .NET Framework, and replacing EF6 with EF Core during the framework migration introduces unnecessary risk and scope.

Rules

Retain EF6 during migration — Keep EntityFramework / EntityFramework.SqlServer packages throughout SDK conversion, package compatibility, and multitargeting phases
Do not replace EF6 with EF Core — Never swap EntityFramework for Microsoft.EntityFrameworkCore.* as part of the framework migration
EF6 is compatible with modern .NET — The EntityFramework 6.5+ package supports net8.0+ via netstandard2.1. Upgrade to the minimum EF6 version that supports the target framework
EF Core migration is a separate effort — Migrating from EF6 to EF Core is a post-migration activity, performed only after the project fully runs on modern .NET
Assessment should flag, not act — When EF6 usage is detected during assessment, note it as a future post-migration task, not a migration blocker or in-scope work item

When This Applies

Package compatibility analysis: Do not flag EF6 as incompatible. Find the minimum EF6 version supporting the target framework.
Multitarget migration: EF6 APIs are available on modern .NET via EF6 6.5+. Do not introduce #if guards to swap EF6 for EF Core.
Assessment reports: List EF6 usage as a post-migration consideration, not as a migration action item.
SDK-style conversion: EntityFramework PackageReference should be preserved as-is.

What NOT to Do

Do not add Microsoft.EntityFrameworkCore packages during any migration phase
Do not remove or replace EntityFramework references
Do not treat EF6 DbContext/model classes as migration blockers
Do not create EF Core DbContext alternatives during framework migration

More from this repository

same repository

launching-iisexpress

twsouthwick/fx2dotnet

Launch a .NET Framework ASP.NET project using IIS Express from the command line, replicating how Visual Studio would run it. Use when the user wants to start, run, or test the web app locally during migration. Do NOT use for .NET Core or modern .NET apps — use dotnet run instead.

2026-04-282

owin-identity

twsouthwick/fx2dotnet

Addressing ASP.NET Identity dependency while upgrading from ASP.NET (.NET Framework) to ASP.NET Core.

2026-04-282

systemweb-adapters

twsouthwick/fx2dotnet

System.Web adapters migration policy for ASP.NET Framework to ASP.NET Core. Use when: migrating System.Web.HttpContext, HttpRequest, HttpResponse, IHttpModule, IHttpHandler, HttpApplication, Global.asax, or other System.Web types to ASP.NET Core. Adapters are the DEFAULT approach during migration to minimize code changes. Covers adapter packages, property translations, incremental IHttpModule/IHttpHandler support, and behavioral differences (lifetime, threading, buffering). Native ASP.NET Core rewrite is a post-migration optimization.

2026-04-282

windows-service-migration

twsouthwick/fx2dotnet

Windows Service migration policy for .NET Framework ServiceBase to modern .NET BackgroundService. Use when: migrating System.ServiceProcess.ServiceBase, ServiceInstaller, ServiceProcessInstaller, or TopShelf-hosted services. The Generic Host + BackgroundService + Microsoft.Extensions.Hosting.WindowsServices pattern is the default approach. Both hosting packages target netstandard2.0 and .NET Framework 4.6.2+, enabling multitarget-first migration. Native rewrite from ServiceBase to BackgroundService can happen while still on net472.

2026-04-282

copilot-customization-advisor

twsouthwick/fx2dotnet

Recommends the right GitHub Copilot customization type (instructions, prompt files, skills, agents, sub-agents, hooks) for a given intent. Use when the user asks which customization to use, whether something should be a skill or agent, or how to structure Copilot repo customizations.

2026-04-102

copilot-customization-skill-authoring

twsouthwick/fx2dotnet

Create and review skill files in .github/skills/. Use this skill when asked to create a new skill, review an existing skill, or improve skill quality. Applies best practices from agent-skills-best-practices.md to ensure skills are concise, discoverable, and effective.

2026-04-102

name	ef6-migration-policy
description	EF6 to EF Core migration policy for .NET Framework to modern .NET upgrades. Use when: assessing EF6 usage, planning package compatibility, multitargeting projects with Entity Framework 6. EF Core is NOT supported on .NET Framework — EF6 packages must be retained during framework-to-modern-dotnet migration and only migrated to EF Core as a separate post-migration effort.

EF6 Migration Policy

Policy

Rules

Retain EF6 during migration — Keep EntityFramework / EntityFramework.SqlServer packages throughout SDK conversion, package compatibility, and multitargeting phases
Do not replace EF6 with EF Core — Never swap EntityFramework for Microsoft.EntityFrameworkCore.* as part of the framework migration
EF6 is compatible with modern .NET — The EntityFramework 6.5+ package supports net8.0+ via netstandard2.1. Upgrade to the minimum EF6 version that supports the target framework
EF Core migration is a separate effort — Migrating from EF6 to EF Core is a post-migration activity, performed only after the project fully runs on modern .NET
Assessment should flag, not act — When EF6 usage is detected during assessment, note it as a future post-migration task, not a migration blocker or in-scope work item

When This Applies

Package compatibility analysis: Do not flag EF6 as incompatible. Find the minimum EF6 version supporting the target framework.
Multitarget migration: EF6 APIs are available on modern .NET via EF6 6.5+. Do not introduce #if guards to swap EF6 for EF Core.
Assessment reports: List EF6 usage as a post-migration consideration, not as a migration action item.
SDK-style conversion: EntityFramework PackageReference should be preserved as-is.

What NOT to Do

Do not add Microsoft.EntityFrameworkCore packages during any migration phase
Do not remove or replace EntityFramework references
Do not treat EF6 DbContext/model classes as migration blockers
Do not create EF Core DbContext alternatives during framework migration