Perform the action in the host application that will run the VBScript code that you want to debug. On the Debug menu, select Break All (or press Ctrl+Alt+Break).The Solution Explorer opens and lists one or more occurrences of AMScriptHost. If the Attach Security Warning dialog appears, click Attach. For example, to debug a Meridian PowerWeb session, select w3wp.exe. In Available Processes, select the name of the executable for the host application that you that you started in step 1 and click Attach.The Available Processes list refreshes to show additional processes. Enable Show processes from all sessions.On the Tools menu, select Attach to Process.
The name of the project is irrelevant because you will not add any code to the project and will discard it when you are finished using the debugger. The key to debugging VBScript from applications other than PowerUser is the ability of Visual Studio to attach itself to those applications.
#.vbs script debugger windows#
The Meridian vault configuration is cached by your browser during each Meridian PowerWeb session. To debug VBScript running in a Meridian PowerWeb session, the debugging tool must be installed on the computer running Internet Information Services and you must have administrative rights on the computer.Although the method described below can also be used with PowerUser, installing and using the Microsoft Script Debugger is just as effective and more convenient. Provides a link to the Microsoft Script Debugger as described in Microsoft Script Debugger. The tool to use depends on the client application where you want to debug the script: For real debugging, you need a different tool. The Visual Studio programmer has the convenience of a debugger built into that development tool but beyond the script validation feature of the Meridian Enterprise Script Editor, you cannot debug VBScript in the editor.
0 kommentar(er)
