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:
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