An Alintex script consists of one or more script files, each of which may be in a different .NET language.  The first script file is called the primary script, while any subsequent script files are referred to as sub scripts.  The primary script contains the script's entry point, which may be provided through a script #region, or a traditional language entry point construct.

 

In the example below, rateOfReturn.vbx is the primary script, while maths.cs, log.vb and resultDialog.vj are sub scripts.

 

> axscript rateOfReturn.vbx maths.cs log.vb resultDialog.vj

 

Any script file automatically references types contained in a subsequent script file.  No special settings or reference statements are required.  For further information see Reusing Code and .

 

Typically a script is named, and referred to, by the name of the primary script.  In the example shown above, one would state that one is running the rateOfReturn script.  A number of non-standard file extensions are supported to help identify primary, sub and executable scripts.

 

Sub scripts typically perform a supporting role, providing program functionality to script files specified ahead of them on the command line.  Because they can be reused in multiple scripts, they offer an effective form of code reuse.

 

Scripts can be packaged into Portable Script (.psf) Files, which provide a convenient way to distribute scripts together with their settings and author information.

 

 

See Also

 

File Extensions | Reusing Code