Per Magne Skuseth
Aug 20, 2013
(1 votes)

Quick tip: EPiServer, Visual Studio 2013 Preview & IIS Express issue

I installed Visual Studio 2013 Preview a little while ago, and have not had any serious issues with it. However, when running a site using IIS Express, edit mode just showed a blank page, rendering it useless.


The fix was pretty simple: uncheck enable browser link in VS:


After doing this, things were back to normal.
If you want to know more about the new “Enable Browser Link” feature, you can read more about it here.
Please note that this is a VS issue, and not an EPiServer issue, which will be fixed in the upcoming release of VS.

Adding error messages and keywords below, so it will turn up in search results as well (you can stop reading now).

artery // Uncaught ReferenceError: WebForm_AutoFocus is not defined // __vwd/js/artery // SyntaxError: missing ; after for-loop condition

Aug 20, 2013


Aug 26, 2013 09:56 PM

Depressing that browswr link is causing this. I saw that umbraco cms was also having problems with browser link.

Hope you've filed a bug on vs2013 feedback for this because browser link looks quite promising.

Per Magne Skuseth
Per Magne Skuseth Jan 19, 2014 01:31 PM

This has been fixed in the official release of vs 2013.

Mark Price
Mark Price Aug 15, 2016 06:08 PM

Annoyingly, the bug appears to be back in Visual Studio 2015!

Last week I was happily using Visual Studio 2015 with Update 3 to create several Episerver sites including Alloy, but this morning Edit View was broken in all my sites. Interestingly, it *almost* worked in Firefox but was completely blank in Microsoft Edge and Chrome. I have *no* idea what I changed to break it.

Googling for "episerver edit view blank" and similar suggested fixes such as clearing the Temporary ASP.NET Files folder, re-installing Visual Studio, resetting IIS and so on. Finally I decided to install Visual Studio 2013 and open the same projects. Everything worked. Opening the same projects again in VS2015--broken Edit View! Both had Browser Link enabled, but I decided to try disabling Browser Link only in VS2015. Success!

A quick Google led to this page. If only I had considered Browser Link to be the problem earlier!

Per Magne Skuseth
Per Magne Skuseth Aug 16, 2016 09:35 AM

Mark: Perhaps the error you got was related to the Visual Studio Web Accessibility Checker? See these threads:

Mark Price
Mark Price Aug 19, 2016 10:12 AM

Yes, Per, I think you're right. At least I now can reenable Browser Link if I disable that extension.

Please login to comment.
Latest blogs
Translating Optimizely CMS 12 UI components

Optimizely CMS 12 have been out for a while now, but still some elements haven't been properly translated resulting in a GUI defaulting to english....

Eric Herlitz | Jan 26, 2023 | Syndicated blog

Image preview in Optimizely CMS12 all properties view

With these simple steps, you can now see an Image and its Metadata, including size and dimensions, when editing an Image property in Optimizely...

Tomas Hensrud Gulla | Jan 26, 2023 | Syndicated blog

Setting up the ImageEditor in Optimizely CMS 12

Setting up certain configurations on Opimizely CMS 12 differs quite a bit from prior versions of (Episerver CMS 11 and older). Here's a small guide...

Eric Herlitz | Jan 25, 2023 | Syndicated blog

Happy Hour Returning in February

Hi everyone! It's been a while and we're excited to resume our Happy Hour in February for more learning, sharing, connecting, relaxing, and just to...

Patrick Lam | Jan 24, 2023