Home | Blog | Terms of service

Audio & Multimedia

Web Development

System Utilities

Home & Hobby

Education

Servers

Security & Privacy

Games & Entertainment

Network & Internet

Desktop

Development

Active X

Basic, VB, VB DotNet

C / C++ / C#

Compilers & Interpreters

Components & Libraries

Debugging

Delphi

Help Tools

Install & Setup

Management & Distribution

Other

Source Editors

Business

Communications

Graphic Apps

wsh editor ^{2 3 4 5}

jscript editor ^{2 3 4 5}

automation ^{2 3 4 5}

scripting ide ^{2 3 4 5}

network administration ^{2 3 4}

debug scripts ^{2 3 4}

windows scripting ^{2 3}

remote machine ^{2 3}

vbscript editor ^{2 3}

scripting tool ^{2 3}

systems management ²

script reference

adsi

windows script host

XLnow OnScript 2.1.568

Released:	2006-12-18
Last Updated:	2007-10-06
License:	$75.00
Publisher:	XLnow
Language:	English, German
Platform:	Windows
Requirements:	Windows Script Host
Install:	Install and Uninstall
Downloads:	249
	Suggest to Friend
	Add to Watch List

Publisher's Description:

XLnow OnScript - XLnow OnScript is an integrated tool for writing, maintaining and running scripts on Microsoft Windows desktop and server systems. With OnScript you can:

Create VBScript and JScript files, Windows Script Files and Script Components from template files with a predefined structure. Use Wizards to create valid .WSF and .WSH scripts. .BAT, .CMD, .HTA, .TXT and .INI files are supported as well - as are the PerlScript and Python script languages. Add custom file types, for example Transact-SQL.

Edit script documents with the assistance of our optimized-for-scripting customizable syntax coloring, statement completion and pop-up parameter lists. Set bookmarks in your documents, find and replace text and save settings in workspaces.

Easily locate information in the script language help files while editing or when your scripts report errors. Use breakpoints for debugging and manage references to additional help files.
Organize collections of sample scripts, code snipplets and production scripts in libraries and share them with others.

Browse the system's type libraries for COM components and explore their objects, methods and properties. Add code that creates objects and references properties and methods without typing. Register your own Script Component Files and reuse them. Keep frequently used components in the Favorites list for quick access.

Run scripts using the Windows Script Host cscript or wscript commands or by the native OnScript Host. Supply parameters, select jobs and view the script output in OnScript. Interact with idle scripts; build applications with multiple scripts that interact at runtime.

Network Edition: Connect to remote machines on your LAN, WAN or through a VPN and access scripts on their local file systems, all from your desktop. Monitor running scripts and view who started them, when and with which parameters. Get notified of changes to shared script files.

Latest Changes:

Outline VBScript and JScript files: Go to Initialization & Declaration, Find Object/Member or ProgID in Object Browser

User License Agreement:

Please see http://www.onscript.com/eula

Screenshot:

QA Report:

Virus Scanning Report

Download Now
File Size: 4.9 Mb

Social bookmarks:

RSS:

Text link code :
Hyper link code:
UBB/BLOG code:

Latest User Reviews:

CPeters

2008-01-16 14:07:37

Version: 2.1.568

Nested script problems

My intent in downloading the app. was to find an IDE for developing .WSF scripts that call .VBS, .JS, and .WSC scripts. I found a few bugs in the program:
- There is no list of XML elements available from the XML schema for .WSF files. The New WSH File Wizard does a pretty good job with a few of them (job, object, reference, script) but leaves out all the rest (xml, package, comment, name, resource, runtime, named, unnamed, usage, example). Nor is there any list of attributes of an element once it is inserted. There should be better or more flexible intellisense.
- The Outline tab doesn't show anything for a .WSF file, except the file itself.
- There is no way to set one file as the starting point for debugging. It is whatever window is active, so if you're working on the called script, you must keep changing back to the calling script window to run it.
- The calling script allows edit and continue without saving to file, but the called script must be saved for changes to take place even though it is open in the designer.
- The same problem exists for all the scripting hosts, including the OnScript host: line numbers reported do not indicate the script file being run, rather they indicate the calling script. If a VBScript in WSHFile1.wsf calls a function in VBScript1.vbs, and an error occurs on line 13 of VBScript1, the error is reported as
"C:\..\OnScript\WSHFile1.wsf(13, 6)
Microsoft VBScript compilation error: "
- The file marked with a red X in the Scripts tab is also the wrong file. In nested calls this causes many problems.
- The Helps tab should be renamed "Help".
- There are other things, but I have no time to continue.
I will say that I think your method for requiring feedback is excellent and most rigorous. If you will take the feedback and make actual changes I think you have a superior structure in place for developing applications.
Außer diesem ist es ausgezeichnet.

Social bookmarks:

RSS:

Download Now
File Size: 4.9 Mb

XLnow OnScript 2.1.568

Publisher's Description:

Latest Changes:

User License Agreement:

Screenshot:

QA Report:

Social bookmarks:

Latest User Reviews:

Nested script problems

Social bookmarks:

Write a Review and Rate XLnow OnScript

Top queries

Last queries