NS Basic/Desktop 4.0 Release Notes Jun 25, 2009 Copyright NS BASIC Corporation |
NS Basic/Desktop 4.0 is a major update to NS Basic/Desktop, a tool to create apps for Windows desktop systems. We created this product since we saw a need for a development tool for desktop systems that would be as easy to use as our tools for handheld systems.
NS Basic/Desktop has an IDE that is similar to that of classic Visual Basic. The programming language is based on Microsoft's VBScript, which was designed as an easy to use, lightweight scripting language. It's solid and offers reasonable performance. When we realized the designers of VBScript had made it easy to add extensions to the language, it became possible to make a serious development tool.
We added extensions to the language in a couple of areas. Statements and functions were added to make the language complete enough for most applications. A set of standard intrinsic controls (Textbox, CommandButton, Popup and others) were added, so apps with a proper Windows look and feel could be created.
Most significantly, we added a powerful mechanism to use standard ActiveX controls. Thousands of these are available from Microsoft and third party developers. There is an ActiveX control for virtually every conceivable purpose: most are easily used from NS Basic/Desktop.
This allows NS Basic/Desktop programs to do some cool things. Besides providing all the usual features of a programming language, NS Basic/Decktop programs can easily interface with COM aware applications, such as Word, Excel and Outlook.
There are other things we did that are also important. The compiler produces a standalone exe file that is secure and easy to distribute. Unless you use ActiveX controls, no runtime libraries or installer are needed (not even MFC). Programs can be debugged using Microsoft's standard Script Debugger.
The implementation of NS Basic/Desktop is similar to NS Basic/CE. Code is almost completely portable between the two environments. The differences you will notice are in the screen size (Windows CE devices generally have much smaller screens) and the need to use versions of ActiveX controls that are designed for desktop versions of Windows.
See the "What's New" section for a detailed list of what is changed from previous versions.
Please visit our web site for the latest version of this document. You'll see the latest installation notes and updated news.
NS Basic/Desktop is a commercial software product, licensed subject to the License Agreement that must be must be agreed to before installation. The Agreement also appears in the NS Basic/Desktop Handbook.
If you are using the Demonstration Edition...
Welcome! You're running a complete copy of NS Basic/Desktop with just a few restrictions:NS Basic/Desktop Features
If you have problems during installation, see Tech Note 01 for common solutions. The hotlinks in this section work if you are reading this document from the CD. Otherwise, if you downloaded the files, click on the file names on your system.
Using the Microsoft Script Debugger
You don't need this to develop NS Basic/Desktop apps, but it can be a big help in debugging. Download it from Microsoft and install it. You will also need to add the statement AllowDebug=True to your program.
Installation Problems
See Tech Note 01 for solutions to common problems.
You can develop programs using NS Basic/Desktop on the following platforms:
To use the NS Basic/Desktop Desktop, you need to have the following:
What's New
4.0.1
4.0.0
Documentation Changes for Version 4.0.0
GetResource(Name[, [filename, register]])
This powerful function allows you to do a number of things to resources contained in your app. The resources must already exist in your app: they must first be added in the IDE as Resources of type 'File' in the Project Explorer of the IDE.
Use this function to:
Complete documentation can be found in the Language Reference. See the "Resources" sample for more info.
NSCEPictureBox.ResourceBitmapIDstr: This property gives the name of a bitmap (.bmp) resource to be displayed in a picturebox. The .ResourceFile property must also be set with the name of the file (an exe or dll) that contains the bitmap resource. It is similar to the .ResourceBitmapID resource, which only takes a resource number. The name must be in upper case.
Example:
myPicturebox.ResourceBitmapIDstr = "GRADIENTBUTTON"See the "Resources" sample for more info.
Notes and Warnings
Documentation
Support
We're committed to delivering the best possible support. The following resources are available: