humbletech99
Programmer
Hi,
I'm new to vbs+wsh and have been learning it this weekend. I used to do wscript //D name.vbs to run the name.vbs and catch any error that was raised, but somehow this is not working now and if I put in a bogus line into the script to force the error, the Windows Scripting Debugger which I have installed does pop up but execution falls through and I get standard windows scripting host pop up of the error as though it had not been run through the debugger.
Any ideas why this behaviour has changed and how I can change it back?
I'm new to vbs+wsh and have been learning it this weekend. I used to do wscript //D name.vbs to run the name.vbs and catch any error that was raised, but somehow this is not working now and if I put in a bogus line into the script to force the error, the Windows Scripting Debugger which I have installed does pop up but execution falls through and I get standard windows scripting host pop up of the error as though it had not been run through the debugger.
Any ideas why this behaviour has changed and how I can change it back?