Visual Studio 2013 Browser Link breaks Reporting

[NerdBrick]

This is more of an FYI learned with VS 2013 and Reporting Q3 2013. 

When the web.config has the debug flag set to true, Reporting wouldn't render in the browser because VS is adding this into the pages which breaks the Telerik js parser. 

<!-- Visual Studio Browser Link -->
<script type="application/json" id="__browserLink_initializationData">
    {"appName":"Chrome"}
</script>
<script type="text/javascript" src="http://localhost:59901/dba793e767684166b11416be8550cb2a/browserLink" async="async"></script>
<!-- End Browser Link -->

This section of the ReportViewer-7.2.13.1016.JS code that it's hitting trying to load and parse the report page in an MVC webapp.
 

beginGetPage: function(pageNo) {
                   throwIfNotInitialized();
                   $.when(loadAsync()).then(function() {
                       onBeginLoadPage(pageNo);
                       return getPageAsync(pageNo);
                   }).done(function(info) {
                       onPageLoadComplete(pageNo, info);
                   }).fail(function(xhr, status, error) {
                       onError(formatXhrError(xhr, status, error));

The error message is "Unexpected Token" from the VS injected block

To fix this you have to turn off vs:EnableBrowserLink in the Web.config 
<add key="vs:EnableBrowserLink" value="false"/>
http://blogs.msdn.com/b/webdev/archive/2013/06/28/browser-link-feature-in-visual-studio-preview-2013.aspx

I see this was also reported as a problem with the Rad controls too. 
http://www.telerik.com/community/forums/aspnet-ajax/grid/browserlink-in-visual-studio-2013-breaks-rendering.aspx 

I'm not relying on VS Browser Link, but just wanted to put this information out there for other's that have a problem.

[Stef]

Hello,

Thank you for your post and detailed information on the topic. Indeed you need to disable the Browser Link feature in Visual Studio 2013 to run projects with the new HTML5 Report Viewer version 7.2.13.1016.

The issue is fixed in the consecutive internal builds.

Regards,
Stef
Telerik