Thursday, June 14, 2012 10:05 PMWhy can't I set a breakpoint while JIT debugging a WSF-based VBScript in Visual Studio 2010? Using the command "WSCRIPT.EXE //x <path-to-WSF-file>" the "Visual Studio Just-In-Time Debugger" dialog presents as expected and I can enter the debugging environment in VS2010. But upon attempts to set a breakpoint on any line I get "This is not a valid location for a breakpoint". Using the same exact WSF file but selecting "New instance of Visual Studio 2008" instead of "New instance of Microsoft Visual Studio 2010" in the "Visual Studio Just-In-Time Debugger" dialog to use VS2008 instead of VS2010 works just fine -- I am able to set breakpoints. Also, I am able to set breakpoints in VS2010 when JIT debugging VBScript in a VBS file. So the only combination that does not work is WSF-based VBScript using VS2010. What gives here; and any way to fix it? Maybe VS2012 will fix?
- Edited by Bob Zimmerman Thursday, June 14, 2012 10:08 PM
Monday, June 18, 2012 2:40 AMModerator
Thank you for posting in the MSDN forum.
Not a VB expert, to make this issue clearly, if possible, you could share us a sample, please attach your Visual Studio project, you can upload it to the sky driver, and then share the download link in your post.
Please also attach a screenshot image in your post. You could share us the detailed steps about how to debug your app. We will try to debug it.
In addition, the VS2012 RC has been released, and if possible, you could try to check it.
If there's any concern, please feel free to let me know.
Jack Zhai [MSFT]
MSDN Community Support | Feedback to us
Wednesday, February 13, 2013 3:21 PMI have exactly the same Problem. Has anyone a solution/an explanation for this?