if the code runs into an vbs error in a VS debug session, no step through in vbs code is provided by VS. instead a popup dialog appears prompting for another VS debug session with the message: "The Just-In-Time was launched without necessary security permission.
To debug this process, the Just-In-Time debugger must be run as an Administrator. Would you like to debug this process?"
if I hit yes, another VS debug session opens with nothing loaded (no script documents) and the origin VS debug session jumps to the managed code exception line being thrown, also no vbs document to be seen.
Im running my VS session as administrator and also passing the debug flags initiating the VBScriptHost class.
Aug 30, 2016 at 9:22 PM
We can't reproduce the Visual Studio security errors you're seeing. What kind of application are you working on (console, WPF, ASP.NET, etc.)?
If you can get past the security issues, try the following:
- Insert a
stop statement somewhere at the beginning of your script.
- Make sure to use
- Run your application outside the debugger. When you get the JIT prompt, select "Manually choose the debugging engines" and click Yes. When prompted, select the script debugging engine. The debugger should attach and navigate to the
stop statement line.