Problem upgrading from 315 to 329: Directory does not exist. Parameter name: directoryVirtualPath

Topics: Installing BugNET
Sep 3, 2014 at 9:58 AM
Edited Sep 3, 2014 at 9:59 AM
I have upgraded this without trouble at least ten times before.

This time I backed up the database and followed the usual instructions. My install is a stock SQL Server install - nothing fancy, upgrades have been 100% reliable etc.

However on restarting the new 329 website, I get the following error/ YSOD. Fortunately it looks like this is the initial compile of 329, so it did not as far as I can tell change the database, in so much as I did not restore the backup, but 315 still seems to work with the database as is. Any ideas? Looks like there's some new bundling code in there which doesn't work if the site is stand-alone (not in a virtual folder).

Here's the error:
Server Error in '/' Application.

Directory does not exist.
Parameter name: directoryVirtualPath

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.ArgumentException: Directory does not exist.
Parameter name: directoryVirtualPath

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace: 


[ArgumentException: Directory does not exist.
Parameter name: directoryVirtualPath]
   System.Web.Optimization.Bundle.Include(String virtualPath, IItemTransform[] transforms) +136
   BugNET.BundleConfig.RegisterBundles(BundleCollection bundles) +587

[HttpException (0x80004005): Directory does not exist.
Parameter name: directoryVirtualPath]
   System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +12951237
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +175
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475

[HttpException (0x80004005): Directory does not exist.
Parameter name: directoryVirtualPath]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12968244
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12807949

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18446
Sep 3, 2014 at 10:07 AM
There's another post here which suggests it's (now) mandatory to put this in a virtual directory. It was previously not so. If that's true, then that could be what is causing this - it looks like the bundling code you have there is assuming there is a virtual directory. When our users go home I can try to install the stuff somewhere else then put it in a virtual directory on IIS, maybe that will fix it.
Coordinator
Sep 3, 2014 at 3:15 PM
philw wrote:
There's another post here which suggests it's (now) mandatory to put this in a virtual directory. It was previously not so. If that's true, then that could be what is causing this - it looks like the bundling code you have there is assuming there is a virtual directory. When our users go home I can try to install the stuff somewhere else then put it in a virtual directory on IIS, maybe that will fix it.
BugNET has always required that you create a virtual directory and configure it as an application in order to execute asp.net properly. This hasn't changed between the releases so I am unsure why you receive that error.
Sep 3, 2014 at 3:33 PM
<shrug> It has worked previously without issue, as a simple website. This new version appears to change that; the previous version still works fine as a simple website.
Sep 4, 2014 at 9:44 AM
Ok, so I un-installed it all and repeated the documented steps in the install guide here, and I still get the same error. I don't really want a virtual directory, or the alias which comes with it, but even if I have one, I'm getting the same error. I guess this upgrade isn't going to work for us. Either someone else will have the same problem, or if it's just us then we can try to fix it in a future release, or look at other options, but this one doesn't work for us I'm afraid. It looks like the bundling code.
Jan 20, 2015 at 3:05 PM
Just to complete this, I could not get 329 to install for reasons above.

However I just upgraded 315 directly to 1.6.339.0 and that works ok, at least it does not throw this error. So I still don't have a virtual directory, but now it's back to not caring about it. Whatever, this may help someone.