I am trying to get bundling to work in ASP.NET MVC 4. I am getting a 404 error from the link generated for the bundled CSS. I have done the following:
Installed the "Microsoft ASP.NET Web Optimization Framework" package via NuGet (v4.0.20710.0)
Created a BundleConfig class in the App_Start dir with the following contents:
using System.Web.Optimization;
namespace BsdAppTemplate.Web_Nancy.App_Start
{
public class BundleConfig
{
public static void RegisterBundles(BundleCollection bundles)
{
bundles.Add(new StyleBundle("~/bundles/styles/cvi").Include(
"~/mainstyles.css"
));
}
}
}
Added the following to Web.config at site root:
<system.web>
<compilation debug="false" targetFramework="4.5" />
<pages>
<namespaces>
<add namespace="System.Web.Optimization"/>
...
</namespaces>
</pages>
</system.web>
Added the following to the head element of my MVC layout file:
@Styles.Render("~/bundles/styles/cvi")
Copied the CSS file referenced in BundleConfig ("mainstyles.css") into the root directory of my web project.
When I view the source of a rendered file, I can see the link appears as:
<link href="/bundles/styles/cvi" rel="stylesheet"/>
This link results in a 404 when browsing to it, or viewing the page request in Chrome's network tab.
I have also tried the equivalent on a web form, but I get the same result (404) from the link generated when I add:
<%: Styles.Render("~/bundles/styles/cvi") %>
Found this question via google results, but the problem in my case was Windows 2008 needed this in web.config
to work when compilation debug=false.
<system.webServer>
<modules>
<add name="BundleModule" type="System.Web.Optimization.BundleModule" />
</modules>
</system.webServer>
It worked fine on Win7 dev machine without this.
It seems that you have missed the step in which you apply your configuration by calling RegisterBundles
in Application_Start
:
protected void Application_Start()
{
...
BundleConfig.RegisterBundles(BundleTable.Bundles);
...
}
Usually in cases where the BundleConfig
class is already there (either as a part of the project template or created by NuGet package during the installation) this call is also already present - this is why many tutorials are implicit about it.
You should also be aware that the BundleConfig
class is there for separation of concerns and in order to keep the Application_Start
clean. In simple cases nothing prevents you from registering bundles directly in Application_Start
:
protected void Application_Start()
{
...
BundleTable.Bundles.Add(new StyleBundle("~/bundles/styles/cvi").Include("~/mainstyles.css"));
...
}
I had the same problem that my script bundle suddenly responded with 404. I a solution similar to @fiat answer that I found on this blogpost.
The solution was to remove and add the BundleModule
in the modules part section of the system.webServer
section.
<modules runAllManagedModulesForAllRequests="true">
<remove name="BundleModule" />
<add name="BundleModule" type="System.Web.Optimization.BundleModule" />
</modules>
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With