Search

Error: The breakpoint will not currently be hit. This location could not be mapped to client side script. when client side debugging by ImarSpaanjaars

Active

4
0
Sign in
 to vote
Type: Bug
ID: 521390
Opened: 12/20/2009 6:12:04 AM
Access Restriction: Public
1
Workaround(s)
2
User(s) can reproduce this bug
When trying to debug valid client side script in a complex scenario (script inside a Content block inside a page using a Master Page, with a ScriptManagerProxy), I get the following error when trying to debug client side script:

The breakpoint will not currently be hit. This location could not be mapped to client side script

Odd thing is, if I copy and paste parts of the page or project to a new Web Site Project, debugging seems to work most of the times. It seems to be the combination of things in this project that makes it fail.

I am using Windows 7 RTM in a Virtual PC. I can successfully debug simple bits of JavaScript code in other Web Site Projects on the same machine. The attached project can be used to reproduce the problem
Details (expand)

Product Language

English

Version

Visual Studio 2008

Operating System

Windows 7

Operating System Language

English

Steps to Reproduce

1. Unzip and open the attached Web Site Project, my Planet Wrox sample web site.

2. Open WebServices.aspx from the Demos folder and set a breakpoint at line 16 that declares a variable called yourName:

var yourName = $get('YourName').value;

3. Open NameService.cs from the App_Code folder and set a breakpoint at line 26 that returns the formatted name from the HelloWorld method:

return string.Format("Hello {0}", yourName);

4. Open WebServices.aspx from the Demos folder again and hit F5 to start debugging

5. Enter some text and hit the Say Hello button

Actual Results

The code breaks at the breakpoint in the Web Service file NameService.cs. The client side breakpoint in WebServices.aspx is completely ignored.

If I enter debugger on a line before the client side JavaScript code I want to debug in WebServices.aspx , everything works fine and I can successfully debug the client side script

Expected Results

The client side JavaScript breakpoint in WebServices.aspx is hit so I can debug client side JavaScript.
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey.

 

File Attachments
File Name Submitted By Submitted On File Size  
PlanetWrox.zip (restricted) ImarSpaanjaars 12/20/2009 -
Sign in to post a comment.
Posted by Microsoft on 7/9/2010 at 3:09 PM
Hello,

We have fixed this issue for the next version of Visual Studio, and once decisions are made regarding servicing releases for Visual Studio 2010 (such as a service pack) this issue will be considered for inclusion in a servicing release.

Best Regards,
Visual Studio Debugger
Posted by Microsoft on 7/9/2010 at 3:05 PM
Hello,

We have fixed this issue for the next version of Visual Studio, and once decisions are made regarding servicing releases for Visual Studio 2010 (such as a service pack) this issue will be considered for inclusion in a servicing release.

Best Regards,
Visual Studio Debugger
Posted by Microsoft on 3/23/2010 at 5:22 PM
Thank you for reporting this. Unfortunatley given the current phase of product development, we were not able to fix this for the Visual Studio 2010 RTM. This will however be a top candidate for fixing after the RTM (such as in a service pack).

Best Regards,
Visual Studio Debugger
Posted by ImarSpaanjaars on 2/2/2010 at 3:06 PM
Not sure what happened, but I tried to log this issue for VS 2010 Beta 2. The scenario I am describing works fine in 2008 / 2008 SP1, but not in VS 2010....
Posted by Microsoft on 2/1/2010 at 5:21 PM
Hello,

Sorry the delay in responding. According to the information you provided, you are using VS2008, not VS 2008 SP1, is that correct? Please install SP1 from http://www.microsoft.com/downloads/details.aspx?FamilyId=FBEE1648-7106-44A7-9649-6D9F6D58056E&displaylang=en

Then please install the following hotfixes for SP1 in the order they are listed. This should address the issue:
http://code.msdn.microsoft.com/KB957912
http://code.msdn.microsoft.com/KB960075
http://code.msdn.microsoft.com/KB967631

Best Regards,
Visual Studio Debugger
Posted by Microsoft on 12/21/2009 at 10:25 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you
Posted by Microsoft on 12/21/2009 at 3:23 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by TomBrown on 10/20/2010 at 1:50 AM
In Visual Studio, clean the solution (right-click in solution exporer and select 'Clean Solution'
Close Visual Studio then:
Delete all temporary ASP.NET files for your project from %Windir%\Microsoft.NET\framework\[version]\Temporary ASP.NET Files\
You may have to reboot before being allowed to delete these temporary files.
Re-open Visual studio. At the place in the html script tag where you want to start debugging, type the word debugger.
When you next debug the solution, the debugger breaks execution at the line with 'debugger' (not on your breakpoints)
© 2012 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement