How to solve the problems caused by VS2013's BrowserLink

In this issue, the editor will bring you the problems caused by VS2013's BrowserLink. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

Environment: vs2013

Problem: an error occurred while calling a WebApi:

So I called the WebApi directly with Fiddler 4, and the status code was 200 (normal), but the JSon indicated that the text was illegal at position 9409.

Looking at it in TextView, a trail of Brow Link was found at 9409:

I actually looked up the FaGui_Html field from the table in the database, which is a Html code that represents a Html page, but before serialization, Vs2013 inserted Browser Link code in front of mine.

Solution: disable Browser Link in Vs2013:

Ticking indicates that it is enabled, but when you click on it, it is disabled.

Start VS2013 again, call the same command again with Fiddler 4, and this time JSOn can parse

Of course, there will be no more Browser Link code in TextView.

Question: I have changed a lot of other record tests, and there is no problem, and I have tested it many times before, but there is no such problem. Why does this problem arise on this record? what is so special about my Html code?

These are the problems caused by the VS2013 BrowserLink shared by the editor. If you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.