- Migrating Documentdb To CosmosMigrates from the deprecated Microsoft.Azure.DocumentDB SDK (V2) to the modern Microsoft.Azure.Cosmos SDK (V3) for Azure Cosmos DB. Use ONLY when Microsoft.Azure.DocumentDB has been flagged as deprecated or obsolete and must be replaced — not for version-bump scenarios where the V2 SDK is still supported.microsoft/upgrade-agent-plugins41
- Migrating Edmx To Code FirstMigrates Entity Framework 6 EDMX-based models (Database-First/Model-First) to EF Core Code-First. Use when upgrading projects containing .edmx files, .Context.tt templates, EntityClient connection strings, or ObjectContext references. Triggers for "migrate EDMX", "convert EDMX to code first", "EF6 to EF Core", "remove EDMX", "database first to code first", and "scaffold DbContext". Also relevant when encountering EntitySQL, EntityObject, or ObjectSet patterns during .NET modernization.microsoft/upgrade-agent-plugins41
- Migrating Ef DbcontextMigrates Entity Framework DbContext registration from Global.asax/Startup to ASP.NET Core dependency injection in Program.cs. Handles both EF6 (classic Entity Framework) and EF Core patterns including connection string migration, DI registration, and database initializer/seeding migration. Use when upgrading ASP.NET to ASP.NET Core projects that use DbContext, Database.SetInitializer, or connection strings in web.config. Also triggers for "migrate DbContext", "register DbContext in DI", "move comicrosoft/upgrade-agent-plugins41
- Migrating Ef6 Code First To Ef CoreMigrates Entity Framework 6 Code-First projects to EF Core. Use when upgrading projects that already use DbContext with Code-First models (no EDMX files) and need to move to EF Core. Triggers for "migrate EF6 to EF Core", "upgrade Entity Framework to EF Core", "convert EF6 Code-First to EF Core", "replace EntityFramework package with EF Core", or "modernize Entity Framework". Also relevant when encountering EF6-specific APIs like EntityTypeConfiguration, DbModelBuilder, Database.SetInitializer, microsoft/upgrade-agent-plugins41
- Migrating Exchange Management ShellMigrate scripts that load the Exchange management snap-in (Microsoft.Exchange.Management.PowerShell.SnapIn / .E2010) off Windows PowerShell 5.1 to PowerShell 7.x, using implicit remoting (New-PSSession -ConfigurationName Microsoft.Exchange) for on-prem Exchange or the Exchange Online (EXO) REST-based module for Exchange Online. Use during the powershell-51-to-7-upgrade scenario for the Exchange snap-in bucket.microsoft/upgrade-agent-plugins41
- Migrating Federated Oidc Token ExchangeMigrates an endpoint that exchanges an external identity provider's workload token for a short-lived application credential — trusted publishing, workload identity federation, federated credentials, OIDC credential exchange. Use when the application accepts a JWT minted for a CI job or service principal by an external issuer, matches its claims against a stored trust policy the application owns, and mints its own API key or token in response. Triggers for "trusted publishing", "trusted publishermicrosoft/upgrade-agent-plugins41
- Migrating Global AsaxMigrates Global.asax application lifecycle events to ASP.NET Core middleware, startup configuration, and Program.cs. Use when upgrading ASP.NET Framework apps containing Global.asax or Global.asax.cs files. Triggers for "migrate Global.asax", "convert application events", "move Application_Start to Program.cs", "replace Global.asax with middleware", and ASP.NET-to-Core migration involving request lifecycle, error handling, or session management.microsoft/upgrade-agent-plugins41
- Migrating Inprocess Background JobsPorts background jobs from ASP.NET Framework to ASP.NET Core and the .NET Generic Host, and stops a job running twice while the legacy and new hosts are both live. Use when an app uses WebBackgrounder (JobManager, IJob, IJobCoordinator, WebFarmJobCoordinator), HostingEnvironment.QueueBackgroundWorkItem, IRegisteredObject or HostingEnvironment.RegisterObject, timers or Task.Run loops started from Application_Start, WebActivatorEx or OWIN Startup, or console job runners whose Main loops and sleepsmicrosoft/upgrade-agent-plugins41
- Migrating Linq To Sql To Ef CoreMigrates LINQ to SQL (System.Data.Linq) data access layer to Entity Framework Core during .NET Framework to modern .NET upgrades. Covers DataContext to DbContext conversion, DBML entity mapping to EF Core model configuration, stored procedure migration, query translation differences, and concurrency handling changes. Use when assessment detects LINQ to SQL usage or when upgrading projects referencing System.Data.Linq. Triggers for "LINQ to SQL", "System.Data.Linq", "DataContext migration", "DBMLmicrosoft/upgrade-agent-plugins41
- Migrating Mvc AuthenticationMigrates ASP.NET MVC and Web API authentication and authorization to ASP.NET Core, covering Forms Authentication, Membership providers, Windows Authentication, token-based auth, authorization rules, and anti-forgery tokens. Use when upgrading projects that use FormsAuthentication, SqlMembershipProvider, SimpleMembership, Windows auth, OWIN OAuth, custom IPrincipal, role providers, ClaimsPrincipal.Current, machineKey, or web.config authorization rules. Also triggers for auth migration, login migrmicrosoft/upgrade-agent-plugins41
- Migrating Mvc BundlingMigrates ASP.NET MVC bundling and minification from System.Web.Optimization to direct script/link tags in ASP.NET Core Razor views. Use when upgrading .NET Framework MVC apps that use BundleTable.Bundles, BundleConfig.cs, ScriptBundle, StyleBundle, @Scripts.Render, or @Styles.Render. Triggers for bundling migration, removing System.Web.Optimization, converting bundle references to static file references, or modernizing script/style includes in .cshtml files.microsoft/upgrade-agent-plugins41
- Migrating Mvc ConfigurationMigrates ASP.NET Framework Web.config configuration to ASP.NET Core appsettings.json and IConfiguration/IOptions patterns. Covers appSettings, connectionStrings, custom config sections, environment-specific transforms, and encrypted config. Use when upgrading projects that use ConfigurationManager.AppSettings, ConfigurationManager.ConnectionStrings, custom IConfigurationSectionHandler implementations, Web.Debug.config/Web.Release.config transforms, or encrypted config sections. Also triggers formicrosoft/upgrade-agent-plugins41
- Migrating Mvc Content NegotiationMigrates ASP.NET Web API content negotiation and formatters to ASP.NET Core equivalents. Converts MediaTypeFormatter subclasses to InputFormatter/OutputFormatter, replaces IContentNegotiator with OutputFormatterSelector, and updates formatter registration from HttpConfiguration.Formatters to MvcOptions. Use when upgrading Web API projects that define custom MediaTypeFormatter classes, configure content negotiation via IContentNegotiator, register XML or JSON formatters, use MediaTypeMapping, or microsoft/upgrade-agent-plugins41
- Migrating Mvc ControllersMigrates ASP.NET Framework controllers and action results to ASP.NET Core equivalents, covering both MVC (Controller) and WebAPI (ApiController) patterns. Use when upgrading controllers that return HttpResponseMessage, IHttpActionResult, use ApiController base class, use Request.CreateResponse(), ResponseTypeAttribute, ChildActionOnlyAttribute, or AsyncController. Also triggers for "convert WebAPI controller", "migrate action results", "replace HttpResponseMessage", "IActionResult migration", anmicrosoft/upgrade-agent-plugins41
- Migrating Mvc Dependency InjectionMigrates dependency injection configuration from ASP.NET Framework MVC and WebAPI projects to ASP.NET Core built-in DI or modernized third-party container integration. Use when upgrading projects that use DependencyResolver.SetResolver, config.DependencyResolver, custom IControllerFactory, custom IHttpControllerActivator, ServiceLocator.Current, or third-party containers (Autofac, Unity, Ninject, Castle Windsor). Also triggers for "migrate dependency injection", "convert DI container", "replace microsoft/upgrade-agent-plugins41
- Migrating Mvc FiltersMigrates ASP.NET MVC global filters and custom AuthorizeAttribute subclasses to ASP.NET Core middleware, authorization policies, and filters. Use for GlobalFilterCollection, FilterConfig, HandleErrorAttribute, IActionFilter/IExceptionFilter conversion, or overrides of AuthorizeCore, OnAuthorization, and HandleUnauthorizedRequest. Covers inherited controller authorization, role/claim equivalence, TempData redirects, response headers, and explicit challenge schemes. Also triggers for MVC-to-Core fmicrosoft/upgrade-agent-plugins41
- Migrating Mvc Http PipelineMigrates ASP.NET Framework HttpModules, HttpHandlers, and Global.asax events to ASP.NET Core middleware and endpoints. Use when projects contain IHttpModule, IHttpHandler, IHttpAsyncHandler, .ashx generic handlers, Global.asax Application_Start/Application_Error/Application_BeginRequest, or web.config httpModules/httpHandlers sections. Also triggers for "convert HttpModule to middleware", "migrate Global.asax", "replace HttpHandler", "pipeline ordering", or when assessment signals include UsesHtmicrosoft/upgrade-agent-plugins41
- Migrating Mvc HttpcontextMigrates ASP.NET Framework HttpContext, Request, and Response usage to ASP.NET Core equivalents. Use when projects reference HttpContext.Current, HttpRequest.InputStream, HttpResponse.Write, HttpServerUtility, Request.ServerVariables, Request.Files, Response.End, Response.AddHeader, or ClaimsPrincipal.Current. Also triggers for "replace HttpContext.Current", "inject IHttpContextAccessor", "async response writing", "request body reading", or when assessment signals include UsesHttpContextCurrent,microsoft/upgrade-agent-plugins41
- Migrating Mvc LoggingMigrates ASP.NET Framework logging and diagnostics to ASP.NET Core built-in logging abstractions, error handling middleware, and health checks. Use when projects use System.Diagnostics.Trace, log4net, NLog, ELMAH, Serilog static loggers, customErrors in web.config, custom error pages, Application_Error, or need health check endpoints. Also triggers for "migrate logging", "replace ELMAH", "convert Trace to ILogger", "add health checks", "migrate error pages", and assessment signals UsesLog4Net, Umicrosoft/upgrade-agent-plugins41
- Migrating Mvc Model BindingMigrates ASP.NET Framework model binding to ASP.NET Core, including binding source attributes, custom model binders, value providers, and over-posting protection. Use when upgrading MVC or Web API projects that use [FromUri], [FromBody], [ModelBinder], [Bind], TryUpdateModel, custom IModelBinder implementations, or ValueProviderFactories. Also triggers for binding source inference with [ApiController], IModelBinderProvider registration, and BindNever attribute migration.microsoft/upgrade-agent-plugins41
- Migrating Mvc Razor ViewsMigrates ASP.NET MVC Razor views to ASP.NET Core by converting HtmlHelpers to TagHelpers, child actions to ViewComponents, porting custom view-location precedence, and updating layout infrastructure. Use when upgrading MVC apps that use Html.ActionLink, Html.BeginForm, Html.TextBoxFor, Html.DropDownListFor, Html.ValidationMessageFor, Html.ValidationSummary, Html.Action, Html.RenderAction, ChildActionOnly, @helper, HtmlString, custom HtmlHelper extensions, or a custom RazorViewEngine / VirtualPatmicrosoft/upgrade-agent-plugins41
- Migrating Mvc RoutingConverts ASP.NET MVC RouteCollection-based routing to ASP.NET Core endpoint routing with MapControllerRoute in Program.cs. Use when migrating RouteConfig.cs, RouteTable.Routes, routes.MapRoute, routes.MapMvcAttributeRoutes, or RouteCollection to ASP.NET Core. Also triggers for MVC routing upgrade, endpoint routing migration, and conventional route conversion.microsoft/upgrade-agent-plugins41
- Migrating Mvc Session StateMigrates ASP.NET Framework session state, TempData, and application state to ASP.NET Core equivalents. Converts HttpSessionState to ISession with distributed cache backend, migrates TempData from session-based to cookie-based provider, and replaces HttpContext.Application and HttpRuntime.Cache with DI-based IMemoryCache or IDistributedCache. Use when upgrading MVC or WebAPI apps that use Session[], TempData[], HttpContext.Application[], HttpRuntime.Cache, or static state patterns. Also triggers microsoft/upgrade-agent-plugins41
- Migrating Mvc Static FilesMigrates ASP.NET MVC static file serving and virtual path providers to ASP.NET Core conventions. Moves Content/, Scripts/, and App_Data/ folders into wwwroot/, configures UseStaticFiles middleware, and replaces VirtualPathProvider with IFileProvider and EmbeddedFileProvider. Use when upgrading MVC apps that serve CSS from ~/Content/, JS from ~/Scripts/, use VirtualPathProvider, serve embedded resources, or store files in App_Data. Also triggers for "configure static files in Core", "wwwroot migrmicrosoft/upgrade-agent-plugins41
- Migrating Mvc System Web AdaptersProvides System.Web Adapters overlay guidance for incremental ASP.NET Framework to ASP.NET Core migration. Installs Microsoft.AspNetCore.SystemWebAdapters compatibility shims so System.Web API patterns (HttpContext.Current, HttpModules, HttpHandlers, Session, ClaimsPrincipal.Current) continue working in ASP.NET Core during the migrate phase, then guides ordered decommission of each shim. Use when assessment signals include UsesSystemWeb, UsesHttpContextCurrent, UsesHttpModules, UsesHttpHandlers,microsoft/upgrade-agent-plugins41
- Migrating Mvc ValidationMigrates ASP.NET Framework validation to ASP.NET Core including data annotations, custom ValidationAttribute classes, ModelState handling, client-side unobtrusive validation, and FluentValidation integration. Use when upgrading projects that use DataAnnotations, IValidatableObject, RemoteAttribute, custom validation attributes with service dependencies, jquery.validate.unobtrusive, or FluentValidation. Also triggers for ModelState.IsValid migration, ApiController automatic 400 responses, Validatmicrosoft/upgrade-agent-plugins41
- Migrating Newtonsoft To System Text JsonMigrates .NET projects from Newtonsoft.Json to System.Text.Json, updating package references, code files, and handling API differences. Use when asked to "migrate Newtonsoft", "switch to System.Text.Json", "replace Newtonsoft.Json", or "upgrade JSON library". Triggers for .csproj/.vbproj files referencing Newtonsoft.Json and .cs/.vb files using Newtonsoft.Json namespaces. Also applies when modernizing .NET dependencies or removing third-party JSON libraries.microsoft/upgrade-agent-plugins41
- Migrating Owin Authentication Handler To CoreMigrates a custom Katana/OWIN authentication handler to an ASP.NET Core authentication scheme. Use when an application defines its own scheme by deriving from the OWIN AuthenticationHandler base class in Microsoft.Owin.Security.Infrastructure — usually with its own AuthenticationMiddleware subclass and IAppBuilder extension — and the equivalent ASP.NET Core handler must be registered with AddScheme. Covers AuthenticateCoreAsync, ApplyResponseChallengeAsync, ApplyResponseGrantAsync, InvokeAsync, microsoft/upgrade-agent-plugins41
- Migrating Owin Cookie AuthMigrates legacy OWIN cookie authentication (Microsoft.Owin.Security.Cookies) to ASP.NET Core cookie authentication (Microsoft.AspNetCore.Authentication.Cookies). Use ONLY when Microsoft.Owin.Security.Cookies has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where the OWIN package is still supported.microsoft/upgrade-agent-plugins41
- Migrating Owin Openid ConnectMigrates legacy OWIN OpenID Connect authentication (Microsoft.Owin.Security.OpenIdConnect) to ASP.NET Core OpenID Connect (Microsoft.AspNetCore.Authentication.OpenIdConnect). Use ONLY when Microsoft.Owin.Security.OpenIdConnect has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where Microsoft.Owin.Security.OpenIdConnect is still supported.microsoft/upgrade-agent-plugins41
- Migrating Owin To Aspnet CoreMigrates OWIN/Katana middleware, authentication, pipeline components, and SignalR 2.x to native ASP.NET Core equivalents. Use when projects reference Microsoft.Owin, IAppBuilder, OwinMiddleware, Microsoft.Owin.Host.SystemWeb, OWIN-based OAuth/cookie/bearer authentication, OWIN startup classes, or SignalR 2.x hubs mapped via OWIN. Triggers for "migrate OWIN", "remove OWIN", "replace OWIN middleware", "convert OWIN pipeline", "migrate Katana", "convert OWIN auth", "upgrade SignalR", "replace OWIN microsoft/upgrade-agent-plugins41
- Migrating Powershell SdkMigrates the legacy System.Management.Automation (PowerShell SDK) references from obsolete .NET Framework (Windows PowerShell 5.1) to modern .NET (PowerShell 7+). Replaces Windows PowerShell Reference Assemblies or GAC references with the cross-platform System.Management.Automation NuGet package. Use ONLY when the legacy Windows PowerShell SDK has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where existing PowerShell packages are still supported. Smicrosoft/upgrade-agent-plugins41
- Migrating Razorengine To RazorlightMigrates the deprecated RazorEngine to RazorLight for Razor template rendering outside of MVC. Use ONLY when RazorEngine has been flagged as deprecated or unmaintained and must be replaced — not for version-bump scenarios where RazorEngine is still supported.microsoft/upgrade-agent-plugins41
- Migrating Semantic Kernel To AgentsMigrates .NET projects from Microsoft Semantic Kernel Agents (Microsoft.SemanticKernel.Agents) to Microsoft Agent Framework (Microsoft.Agents.AI). Handles NuGet package updates, namespace changes, agent creation, tool registration, thread management, and invocation transformations. Use when migrating ChatCompletionAgent, OpenAIAssistantAgent, AzureAIAgent, OpenAIResponseAgent, or A2AAgent to Agent Framework. Triggers for "semantic kernel to agents", "migrate SK agents", "upgrade agents frameworkmicrosoft/upgrade-agent-plugins41
- Migrating Spa Services To Spa ProxyMigrates ASP.NET Core projects from the obsolete Microsoft.AspNetCore.SpaServices.Extensions to Microsoft.AspNetCore.SpaProxy for Angular and React SPAs. Use ONLY when Microsoft.AspNetCore.SpaServices.Extensions has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where SpaServices.Extensions is still supported.microsoft/upgrade-agent-plugins41
- Migrating System SpatialMigrates the obsolete System.Spatial (OData v1–v3 spatial types) to Microsoft.Spatial for OData v4. Use ONLY when System.Spatial has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where System.Spatial is still supported.microsoft/upgrade-agent-plugins41
- Migrating To Microsoft Data SqlclientMigrates .NET projects from System.Data.SqlClient to Microsoft.Data.SqlClient, handling package references, namespace updates, connection string encryption changes, and behavioral differences. Use when upgrading SqlClient, replacing System.Data.SqlClient, migrating to Microsoft.Data.SqlClient, or modernizing SQL Server data access in C# or VB.NET projects (.csproj, .vbproj, .cs, .vb files).microsoft/upgrade-agent-plugins41
- Migrating To Msmq MessagingMigrates .NET projects from System.Messaging to MSMQ.Messaging for .NET Core compatibility. Use when upgrading projects that reference System.Messaging, MessageQueue, XmlMessageFormatter, or when migrating MSMQ queue code from .NET Framework to .NET Core/.NET 5+. Also triggers for queue configuration migration from web.config/app.config to appsettings.json and replacing ConfigurationManager with dependency injection for queue settings.microsoft/upgrade-agent-plugins41
- Migrating Wcf To CorewcfMigrates server-side WCF services from .NET Framework to CoreWCF for .NET 6+. Converts hosting, configuration, bindings, behavior extensions, and APM-style contracts. Use when a project references System.ServiceModel via GAC, contains .svc files, uses ServiceHost, or needs WCF endpoints rehosted in ASP.NET Core. Also handles mixed client/server projects by preserving client packages.microsoft/upgrade-agent-plugins41
- Migrating Webapi CorsMigrates legacy ASP.NET Web API CORS (Microsoft.AspNet.WebApi.Cors) to ASP.NET Core CORS (Microsoft.AspNetCore.Cors). Use ONLY when Microsoft.AspNet.WebApi.Cors has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where Microsoft.AspNet.WebApi.Cors is still supported.microsoft/upgrade-agent-plugins41
- Migrating Webapi OdataGates ASP.NET Framework to Core migrations on externally-consumed wire contracts before migrating Web API OData to Microsoft.AspNetCore.OData. Use when replacing legacy OData or migrating Atom feeds, custom ODataEntityTypeSerializer implementations, or non-OData JSON/XML endpoints with pinned response shapes or explicit repository compatibility hints, even without an OData package. Not for version bumps that retain the existing stack or applications already on ASP.NET Core.microsoft/upgrade-agent-plugins41
- Migrating Webforms To Blazor ServerMigrates ASP.NET Web Forms applications to Blazor Server using Blazor patterns. Handles complete migration: Blazor project setup (side-by-side or in-place), Routes component configuration, App.razor InteractiveServer render modes, static asset migration (Content/Scripts/Images to wwwroot), markup conversion (.aspx/.ascx/.master to .razor), control translation (asp: prefix removal to native HTML/Blazor components), Web Forms expression block conversion to Razor syntax, lifecycle mapping (Page_Loamicrosoft/upgrade-agent-plugins41
- Migrating Wmi To CimMigrate removed WMI cmdlets and type accelerators to CIM in PowerShell 7.x: Get-WmiObject → Get-CimInstance, Invoke-WmiMethod → Invoke-CimMethod, Remove-WmiObject → Remove-CimInstance, Register-WmiEvent → Register-CimIndicationEvent, and [wmi]/[wmiclass]/[wmisearcher] accelerators. Use during the powershell-51-to-7-upgrade scenario for the WMI blocker bucket.microsoft/upgrade-agent-plugins41
- Modernizing Csharp VersionUpgrade C# code to use newer C# language features. Use this skill whenever the user wants to modernize C# code to a specific language version (e.g., "upgrade to C# 12", "use latest C# features", "modernize this C# code"), apply new language features from any C# version 7.0 through 15, or when migrating a .NET project to a newer target framework and the C# language version increases. Also trigger when the user asks about what C# features are available for a given version, wants to know which modemicrosoft/upgrade-agent-plugins41
- Modifying Project PropertiesModifies .NET project properties in PropertyGroup elements within .csproj, .vbproj, and Directory.Build.props files. Handles TargetFramework, LangVersion, Nullable, OutputType, TreatWarningsAsErrors, and other MSBuild configuration settings. Use when asked to "change TargetFramework", "update project settings", "enable nullable", "set LangVersion", or modify any build property. Also triggers for Directory.Build.props changes, conditional PropertyGroup handling, and centralized vs project-specifimicrosoft/upgrade-agent-plugins41
- Newtonsoft Json MigrationMigrates .NET projects from Newtonsoft.Json to System.Text.Json. Use when user wants to replace Newtonsoft.Json, switch to System.Text.Json, migrate JSON library, or modernize JSON serialization.microsoft/upgrade-agent-plugins41
- Nuget Package UpgradeUpgrade one or more NuGet packages from their current version to a target version across a project, several projects, a folder, a solution, or the whole repository. Use when the user wants to bump, update, or upgrade a specific NuGet package (or packages) to a given version or to the latest supported version, detect breaking API changes introduced by the new version, and fix the resulting code. User-initiated — match the user's stated package(s) and version intent.microsoft/upgrade-agent-plugins41
- Post Scenario CompletionGeneric guidance for presenting scenario completion and next-step recommendations to the usermicrosoft/upgrade-agent-plugins41
- Powershell 51 To 7 UpgradeUpgrade Windows PowerShell 5.1 scripts (.ps1/.psm1/.psd1) to cross-platform PowerShell 7.x. Use when the user asks to upgrade PowerShell scripts, move off Windows PowerShell 5.1, migrate WMI to CIM, remove PSSnapins, or make scripts run on PowerShell 7 / pwsh. Covers loose scripts that ship alongside a .NET repo — NOT binary cmdlet/PowerShell-SDK projects (those use the migrating-powershell-sdk lazy skill in the normal .NET version upgrade).microsoft/upgrade-agent-plugins41
- Powershell Mechanical FixupsApply low-risk, deterministic PowerShell 5.1 → 7.x fixes across scripts: '-Encoding Byte' → '-AsByteStream', hardcoded 'powershell.exe' → 'pwsh', removing 'New-WebServiceProxy', bumping '#Requires -Version 5' / dropping '-PSEdition Desktop', pinning explicit '-Encoding' on file writes (the default changed to UTF-8 no-BOM in PS7), and rewriting fragile '$x -eq $null' to '$null -eq $x'. Use during the powershell-51-to-7-upgrade scenario's execution stage to clear the AutoFix-severity findings befomicrosoft/upgrade-agent-plugins41
- Replacing Eventlog With WineventReplace the removed *-EventLog cmdlets (Get-EventLog, Write-EventLog, New-EventLog, Clear-EventLog, Limit-EventLog, Show-EventLog, Remove-EventLog) with Get-WinEvent / New-WinEvent or System.Diagnostics.EventLog in PowerShell 7.x. Use during the powershell-51-to-7-upgrade scenario for the EventLog blocker bucket.microsoft/upgrade-agent-plugins41
- Scaffolding Yarp Proxy ProjectScaffolds a new ASP.NET Core project with YARP reverse proxy alongside an existing .NET Framework MVC or WebAPI project for incremental side-by-side migration. Use when a migration task requires creating a new Core project that proxies to the old Framework app, when the side-by-side migration approach is selected, or when scaffold/YARP/proxy setup is needed. Also handles authentication interop between the two apps (shared cookie or remote authentication) so users stay signed in across both. Alsomicrosoft/upgrade-agent-plugins41
- Scanning Powershell CompatibilityDetect Windows PowerShell 5.1 → 7.x compatibility blockers across a tree of .ps1/.psm1/.psd1 files. Two parts: generate and validate a PSScriptAnalyzer compatibility profile for the target host (the primary detector, covering removed commands/parameters/types), then run a small parser-driven catalog as a sidecar for what PSScriptAnalyzer is structurally blind to — encoding and other behavioral changes, parameter values, type accelerators, module availability, COM, and deprecated-but-present cmdlmicrosoft/upgrade-agent-plugins41
- Sdk Style ConversionConverts legacy .NET projects to SDK-style project format. Use when user wants to convert to SDK-style, modernize project files, or migrate from legacy csproj format. Does not change target frameworks.microsoft/upgrade-agent-plugins41
- Semantic Kernel To Agents FrameworkMigrates .NET projects from Semantic Kernel to the Microsoft Agents Framework. Use when user wants to migrate Semantic Kernel agents, upgrade from SK to Agents Framework, or replace ChatCompletionAgent/OpenAIAssistantAgent with Agent Framework equivalents.microsoft/upgrade-agent-plugins41
- Sharing Authentication Cookies Katana InteropShares authentication cookies between Katana/OWIN applications on ASP.NET Framework and ASP.NET Core applications during side-by-side migrations. Use when both hosts must accept the same cookie, when AspNetTicketDataFormat, DataProtectorShim, or Microsoft.Owin.Security.Interop is needed, or when users must remain signed in while routes move behind YARP or System.Web Adapters.microsoft/upgrade-agent-plugins41
- Sqlclient MigrationMigrates .NET projects from System.Data.SqlClient to Microsoft.Data.SqlClient. Use when user wants to upgrade SqlClient, migrate to Microsoft.Data.SqlClient, or modernize SQL Server data access.microsoft/upgrade-agent-plugins41
- Triaging Powershell Analyzer FindingsDecide whether a PSScriptAnalyzer PSUseCompatibleCommands / PSUseCompatibleTypes finding is a real PowerShell 5.1 → 7.x break or one of four measured false-positive classes: a function defined elsewhere in the estate, an abbreviated parameter prefix such as '-fore', a symbol the compatibility profile dropped during generation, or a provider dynamic parameter such as 'Set-ItemProperty -Type'. Each class has a mechanical test that settles it. Use during the powershell-51-to-7-upgrade scenario's exmicrosoft/upgrade-agent-plugins41
- Typescript Compiler UpgradeUpgrade the typescript npm package (the TypeScript compiler) to a newer version through incremental major-version migrations. Use this when asked to upgrade, update, or migrate typescript itself — especially to TypeScript 7. Do NOT use this for upgrading other npm packages (use typescript-dependencies-upgrade instead).microsoft/upgrade-agent-plugins41
- Typescript Dependencies UpgradeUpgrade a JavaScript or TypeScript project's npm dependencies to their latest or explicitly requested exact versions and resolve breaking changes. Use this when asked to upgrade, update, or modernize npm packages in any JavaScript or TypeScript project — including JavaScript-only projects with no tsconfig.json — whether upgrading all packages or specific ones the user names, except when the user is upgrading the typescript package itself (use typescript-compiler-upgrade instead).microsoft/upgrade-agent-plugins41