Closed damccull closed 9 years ago
cc @jodavis
@jodavis is the issue here that the load is up-to-date, but the loader is loading an older BrowserLink runtime DLL?
Yes, the runtime DLL that's installed with VS must be out of date. There should be a new tools build available soon, which will address the problem. In the meantime, app.UseBrowserLink() needs to be commented out.
Using the latest nightlies + latest dnvm/dnx, with app.UseBrowserLink() in my Startup.Configure() method, I'm getting the following exception. Commenting out that one line immediately brings the page back to a normal state.
Here is my package.json: