migrating-mvc-bundling Skill

Source

• Creator: microsoft
• Repository: microsoft/upgrade-agent-plugins
• Skill file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/web/mvc/migrating-mvc-bundling/SKILL.md

What it does

Migrates 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, re

Skill instructions

ASP.NET MVC Bundling and Minification Migration Converts .NET Framework MVC bundling (System.Web.Optimization) to direct <script/<link tags pointing at static files under wwwroot/. ASP.NET Core serves static files from wwwroot/ instead of using a bundling pipeline, so every bundle reference must be replaced with explicit file references. Workflow Progress: - [ ] Step 1: Inventory bundle registrations - [ ] Step 2: Replace bundle references in Razor files - [ ] Step 3: Remove BundleConfig and related code - [ ] Step 4: Remove System.Web.Optimization usings - [ ] Step 5: Verify build Step 1: Inventory bundle registrations Search for BundleTable.Bundles across the project. The registration is typically in a file named BundleConfig.cs but may be elsewhere. Record every bundle name and its included file paths — these are needed to expand references in Step 2. Example registration to look for: csharp bundles.Add(new ScriptBundle("/bundles/jquery").Include( "/Scripts/jquery-{version}.js"));