Skip to content

Agent does not preserve asset bundling/packaging configuration #1698

@mikadumont

Description

@mikadumont

Description

Direct customer feedback:

After upgrading an ASP.NET MVC application (.NET Framework 4.8 → .NET 8), CSS, icons, and static resources rendered incorrectly due to two issues: (1) the project's EnableDefaultContentItems was set to false, so resources weren't loaded after .NET Framework's bundle tool was removed; (2) no replacement bundling tool was configured.

Expected Behavior:

The agent should detect the existing asset pipeline configuration (e.g., BundleConfig.cs) and either preserve functional equivalence automatically or provide a clear, supported replacement path (e.g., configure webpack or WebOptimizer).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions