If Internet Explorer is configured as a browser during debugging, Visual Studio could theoretically stop at the checkpoints set on the client side of the script. To use this function, you need to make sure that "Disable script debugging" is checked on the tab "IE Internet Options", "Advanced".
However, I found that VS script debugging would be a bit flaky; breakpoint does not always hit, especially with VS2010 or earlier. My personal experience is that it works best in VS2012 or later.
If you use VS as a client debugger script, and you find that your control points on the client side do not fall, it is better to insert a "debugger"; lines to the line you would like to split to make sure that it is matched by the VS script debugger.
pennstatephil posted the link above, which does contain additional information on this subject: http://msdn.microsoft.com/en-us/library/7seh8d72.aspx
Edit: I cannot add comments, but in response to sb9's comment about why IE should be used, I find that debugging in Visual Studio is much more convenient when examining the script behavior before the postback occurs and on the server side the behavior occurs immediately after the postback . In addition, sometimes the VS / IE combination will catch errors that report Chrome and Firefox / Firebug reports with a meaningless error message.
thesentiment
source share