0

I have ASP.NET application where I use MSScriptControl.ScriptControlClass to execute VBScripts. However, breakpoints ('stop') are ignored when Eval() function runs the script. I'd like to see JITDebugger triggered, which would allow me to use Microsoft Script Debugger to debug the script. Has anyone had similar issues?

EDIT: After some investigation I found that due to our IIS settings (we are using Windows Authentication) ASP.NET worker process runs as DefaultAppPool and does not have same privileges or registry set as logged on user. So I guess the question now is "How to change regsitry keys for DefaultAppPool user?"

EDIT2: I asked this question in separate thread and got an answer: How to change registry keys for DefaultAppPool?

Community
  • 1
  • 1
rok14
  • 23
  • 4

1 Answers1

0

The answers to "Debugging script in MS Script Control" list some relevant options and registry values.

If those hints do not help, try to isolate the culprit by systematic checks. Can you debug

  1. a console script without a Script Control
  2. a console script using code via the Script Control
  3. an ASP without a Script Control
Ekkehard.Horner
  • 38,498
  • 2
  • 45
  • 96
  • Hi, thanks for this. 1. I can debug VBScript from cmd, 2. I can debug VBScript using ScriptControl (Eval or Run) from C# console application, 3. I can debug my ASP.NET project, but ScriptControl.Eval ignores breakpoint if the code is running in my ASP.NET project – rok14 Apr 23 '14 at 15:54