migrating-global-asax

Migrate ASP.NET Global.asax lifecycle events to ASP.NET Core equivalents.

19|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-global-asax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrating-global-asax
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/web/aspnet/migrating-global-asax
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-global-asax

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill migrates application lifecycle events from ASP.NET Global.asax to ASP.NET Core equivalents, simplifying the upgrade process for developers.

Core Features & Use Cases

  • Event Migrator: Converts application events like Application_Start to their ASP.NET Core equivalents.
  • Workflow Automation: Automates the process of moving and converting code, reducing manual work.
  • Use Case: Ideal for developers upgrading ASP.NET Framework applications to ASP.NET Core and needing to replace Global.asax.

Quick Start

Migrate your Global.asax to ASP.NET Core with the 'migrating-global-asax' skill.

Frequently Asked Questions about migrating-global-asax

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate ASP.NET Global.asax application lifecycle events to ASP.NET Core?

Migrating ASP.NET Global.asax lifecycle events to ASP.NET Core involves converting Application_Start, Application_End, and other event handlers to their Core architecture equivalents to align with the new framework's startup pipeline.

What is the best way to convert Application_Start from Global.asax to ASP.NET Core?

Converting Application_Start from Global.asax to ASP.NET Core requires moving initialization logic into the new application startup pipeline, replacing the legacy event handler with Core's equivalent lifecycle mechanism to ensure proper execution.

Can I automate code conversion for Global.asax events when upgrading to ASP.NET Core?

Automating code conversion for Global.asax events during an ASP.NET Core upgrade is supported, reducing manual migration work by automatically moving and replacing application lifecycle code to align with Core architecture.

When do I need to replace Global.asax during an ASP.NET Framework to Core transition?

Replacing Global.asax is needed during an ASP.NET Framework to Core transition when your application relies on lifecycle events, requiring conversion of these handlers to Core equivalents to maintain functionality in the new architecture.

Does ASP.NET Core support Global.asax files natively?

ASP.NET Core does not support Global.asax files natively, requiring developers to migrate application lifecycle events like Application_Start to their Core equivalents to ensure the framework's architecture handles them properly.