Browser link giving error

Question

1.00/5 (2 votes)

See more:

Browser Link issue
Error SS

can any one suggest why this error coming after period of time its start giving error

What I have tried:

Browser Link issue
after period of time its start giving error

Posted 26-Aug-16 3:37am

Member-515487

Updated 26-Aug-16 3:48am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

David_Wimbley · Answer 1 · 2016-08-26T03:48:00

That error is browserlink in visual studio. Its meant to update your site in real time when you make changes to css/html. Its not an error to worry about but if you want to disable it you can try the following steps or link below.

Uncheck enable browserlink in the browser link menu item
Set appsetting vs:EnableBrowserLink to false in your web.config

Using Browser Link in Visual Studio 2013 | The ASP.NET Site[^]
Browser Link feature in Visual Studio Preview 2013 | .NET Web Development and Tools Blog[^]

As for you receiving the 404, you can ignore it im sure but it seems as though it was a bug in chrome. They say it should have been fixed but don't detail a version of the fix

WebSockets transport pings the wrong server URL. · Issue #2569 · SignalR/SignalR · GitHub[^]