Directory does not exist. Parameter name: directoryVirtualPath

Answer 1

This can also be caused by a race condition while deploying:

If you use Visual Studio's "Publish" to deploy over a network file share, and check "Delete all existing files prior to publish." (I do this sometimes to ensure that we're not unknowingly still depending on files that have been removed from the project but are still hanging out on the server.)

If someone hits the site before all the required JS/CSS files are re-deployed, it will start Application_Start and RegisterBundles which will fail to properly construct the bundles and throw this exception.

But by the time you get this exception and go check the server, all the necessary files are right where they should be!

However, the application happily continues to serve the site, generating 404's for any bundle request, along with the unstyled/unfunctional pages that result from this, and never tries to rebuild the bundles even after the necessary JS/CSS files are now available.

A re-deploy using "Replace matching files with local copies" will trigger the app to restart and properly register the bundles this time.

Answer 2

Basically stack trace gives you the exact place (as highlighted in screenshot) you need to remove non-existing resource.

Answer 3

I had the same problem and found out that I had some bundles that pointed to non-exisiting files using {version} and * wildcards such as

bundles.Add(new ScriptBundle("~/bundles/jquery").Include(
    "~/Scripts/jquery-{version}.js"));

I removed all of those and the error went away.

Answer 4

Like @JerSchneid, my problem was empty directories, but my deployment process was different from the OP. I was doing a git-based deploy on Azure (which uses Kudu), and didn't realize that git doesn't include empty directories in the repo. See https://stackoverflow.com/a/115992/1876622

So my local folder structure was:

[Project Root]/Content/jquery-plugins // had files

[Project Root]/Scripts/jquery-plugins // had files

[Project Root]/Scripts/misc-plugins // empty folder

Whereas any clone / pull of my repository on the remote server was not getting said empty directory:

[Project Root]/Content/jquery-plugins // had files

[Project Root]/Scripts/jquery-plugins // had files

The best approach to fixing this is to create a .keep file in the empty directory. See this SO solution: https://stackoverflow.com/a/21422128/1876622

Answer 5

I also had this error when I combined all my separated bundles into one bundle.

bundles.Add(new ScriptBundle("~/bundles/one").Include(
            "~/Scripts/one.js"));
bundles.Add(new ScriptBundle("~/bundles/two").Include(
            "~/Scripts/two.js"));

Changed to

bundles.Add(new ScriptBundle("~/bundles/js").Include(
            "~/Scripts/one.js",
            "~/Scripts/two.js"));

I had to refresh application pool on my shared hosting's control panel to fix this issue.

Answer 6

I had created a new Angular application and written

bundles.Add(new ScriptBundle("~/bundles/app")
    .IncludeDirectory("~/Angular", "*.js")
    .IncludeDirectory("~/Angular/directives/shared", "*.js")
    .IncludeDirectory("~/Angular/directives/main", "*.js")
    .IncludeDirectory("~/Angular/services", "*.js"));

but I had created no services, so the services folder was not deployed on publish as it was empty. Unfortunately, you have to put a dummy file inside any empty folder in order for it to publish

https://blogs.msdn.microsoft.com/webdevelopertips/2010/04/29/tip-105-did-you-know-how-to-include-empty-directory-when-package-a-web-application/