All Agent Skills
41,263 results
- Migrating Mvc RoutingMicrosoftOfficialConverts 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.
- Migrating Mvc Session StateMicrosoftOfficialMigrates 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.
- Migrating Mvc Static FilesMicrosoftOfficialMigrates 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.
- Migrating Mvc System Web AdaptersMicrosoftOfficialProvides 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.
- Migrating Mvc ValidationMicrosoftOfficialMigrates ASP.NET Framework validation to ASP.NET Core including data annotations, custom ValidationAttribute classes, ModelState handling, client-side unobtrusive validation, and FluentValidation integration.
- Migrating Newtonsoft To System Text JsonMicrosoftOfficialMigrates .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.
- Migrating Owin Authentication Handler To CoreMicrosoftOfficialMigrates 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…
- Migrating Owin Cookie AuthMicrosoftOfficialMigrates 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.
- Migrating Owin Oauth To JwtMicrosoftOfficialMigrates OWIN OAuth bearer authentication and OWIN-hosted custom Entra ID (Azure AD) token validation to ASP.NET Core AddJwtBearer. Covers Microsoft.Owin.Security.OAuth, JsonWebTokenHandler, TokenValidationParameters, ConfigurationManager and OpenIdConnectConfiguration for JWKS caching, AadIssuerValidator, custom IssuerValidator and IssuerSigningKeyValidator, EnableAadSigningKeyIssuerValidation…
- Migrating Owin Openid ConnectMicrosoftOfficialMigrates 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.
- Migrating Owin To Aspnet CoreMicrosoftOfficialMigrates 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.
- Migrating Powershell SdkMicrosoftOfficialMigrates 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.
- Migrating Razorengine To RazorlightMicrosoftOfficialMigrates 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.
- Migrating Semantic Kernel To AgentsMicrosoftOfficialMigrates .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.
- Migrating Spa Services To Spa ProxyMicrosoftOfficialMigrates 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.
- Migrating System SpatialMicrosoftOfficialMigrates 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.
- Migrating To Microsoft Data SqlclientMicrosoftOfficialMigrates .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).
- Migrating To Msmq MessagingMicrosoftOfficialMigrates .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+.
- Migrating Transient Fault Handling To PollyMicrosoftOfficialMigrates the Enterprise Library Transient Fault Handling Application Block (EnterpriseLibrary.TransientFaultHandling and its .Data, .Configuration, .WindowsAzure.Storage, .ServiceBus and .Caching companions, including the Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.ServiceBus alias) to the modern .NET resilience stack — Microsoft.Extensions.Resilience and the Polly v8 resilience…
- Migrating Wcf To CorewcfMicrosoftOfficialMigrates 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.
- Migrating Webapi CorsMicrosoftOfficialMigrates 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.
- Migrating Webapi OdataMicrosoftOfficialGates 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.
- Migrating Webforms To Blazor ServerMicrosoftOfficialMigrates 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…
- Migrating Wmi To CimMicrosoftOfficialMigrate 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.