Skip to main content

ASP.NET Web Optimizations: 404 not found error

To optimize an ASP.NET MVC application we are using the ASP.NET Optimization framework. During development everything worked fine but the moment we enabled the bundling and minification functionally we started to get 404 errors. These 404 errors were not coming from resources that we loaded directly. Instead they were loaded through some CSS files that were part of our bundles.

This was really some strange and unexpected behavior. What was going in?

The thing is when using the StyleBundle and ScriptBundle classes, the "virtualpath" parameter of the classes DOES matter when  have various folders inside the Content folder that can contain many different sets of styles for various reasons, and you want to maintain that folder structure. In our case we were using the Kendo UI widgets, so we had multiple folders inside our MVC content folder:

image

We fixed this by changing the path to the Kendo CSS to:

bundles.Add(new StyleBundle("~/Content/kendo/2014.1.318/kendostyles").Include("~/Content/kendo/2014.1.318/kendo.common.*", "~/Content/kendo/2014.1.318/kendo.default.*"));

The important thing is that the virtual path matches the folder structure of your content folder.

More information about this issue and how to resolve it can be found in  the following blog post: http://www.mvccentral.net/Story/Details/articles/kahanu/stylebundle-403-error-solved.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more