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.
↧