Choosing a Scripting language with debugging capability line by linefor windows

  • Thread starter Thread starter kishore
  • Start date Start date
K

kishore

Hi ,

I am in need of a scripting language and debugger for Windows ( xp/
2003 etc) , that provides me the ability to create custom commands
inside itself and the ability to debug line by line

These debuggable custom commands will use / call API's written in C+
+ ( visual studio) based application in the back end.

Appreciate suggestion of various alternatives for this problem

PS: I am novice in windows world

Regards >> kishore
 
kishore said:
Hi ,

I am in need of a scripting language and debugger for Windows ( xp/
2003 etc) , that provides me the ability to create custom commands
inside itself and the ability to debug line by line

These debuggable custom commands will use / call API's written in C+
+ ( visual studio) based application in the back end.

Appreciate suggestion of various alternatives for this problem

PS: I am novice in windows world

Regards >> kishore
Click to expand...

The newest scripting environment is Powershell, but I'm not sure if it can
interface at the API level or whether there is a true debugger available
(book on the subject lies unread...). There's no hard and fast definition
of "scripting" but I'd guess most if not all would not provide the
facilities you need. Visual Basic Scripting, often used via Windows
Scripting Host, is another alternative. The standard NT Command shell is
pretty ancient and hard to work with (to anyone who's mastered Unix shells,
anyway).

Best bet is probably Visual Studio Express, which is free. See:
http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express

Alternatively, the Visual Basic for Applications built-in to Word, Excel,
and other Office applications is surprisingly powerful and you can get into
a well-equipped debugger using Alt-F11. You can certainly call out at the
API level.

Phil, London
 
Philip Herlihy said:
The newest scripting environment is Powershell, but I'm not sure if it can
interface at the API level or whether there is a true debugger available
(book on the subject lies unread...). There's no hard and fast definition
of "scripting" but I'd guess most if not all would not provide the
facilities you need. Visual Basic Scripting, often used via Windows
Scripting Host, is another alternative. The standard NT Command shell is
pretty ancient and hard to work with (to anyone who's mastered Unix
shells, anyway).

Best bet is probably Visual Studio Express, which is free. See:
http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express

Alternatively, the Visual Basic for Applications built-in to Word, Excel,
and other Office applications is surprisingly powerful and you can get
into a well-equipped debugger using Alt-F11. You can certainly call out
at the API level.

Phil, London
Click to expand...

I'm not a regular user of PowerShell, but I spotted today that there is now
a graphical debugging environment which might be of use.
http://dougfinke.com/blog/index.php/2009/01/20/next-time-you-need-to-ping-try-powershell-ise/

Phil
 
Back
Top