ASPCompiler Project settings dialog
ASP Compiler 1.1 documentation is under development. See also the examples.

Project settings dialog box


  1. External objects. This is the list of the namespaces available to the script in its original/source form. Namespaces in the active scripting are the global names of objects, variables etc. available for the script when it runs. For example in ASP they are the ASP objects shown on the picture (and some more depending on the ASP version), in WSH there is only one - WScript. Namespaces are defined by the script host.

    • Using the drop-down box and the Apply button you can select standard namespaces for some popular script hosts - ASP and WSH are listed.

    • You can add custom namespaces or remove some of the listed by using these buttons and edit box. If you want to compile a script for a script host not known for the ASPC you will need to add the namespaces manualy.

  2. Paths.These 3 boxes contain the source, output and VBProject paths (read more in ASPC Projects). You can browse to the desired path clicking the buttons on the right or enter relative paths - relative to the directory in which the project is/will be saved. If you want to make your project moveable - for example you want to be able to compile it on another machine.

  3. Project name is an important setting. It determines the VB project name and becomes the first part of the program ID of the every component contained in it.

  4. Save full paths. If checked project will be saved with the full paths to the source and output directories. This can be useful for some advanced tricks but will make the project difficult to move to another location. If a project will be built using the console utility aspc.exe - for example in case of frequent site regeneration using CTS you will need to save a copy of the project with this box checked and pass it to the aspc.exe.

  5. Debug build. This works together with the DbgTrace directive. Using this option you are able to discard from the compiled version (unchecked) the statements marked with the above directive or leave them (checked). See also TraceMsg component.

  6. Translate ASP Tags.What to use for the ASP tags (<%= %>). If you want to use something else and not Response.Write - enter it in this field. For a sample which shows when this trick is useful see the Example10.

  7. Read me. A plain text file (must be in the same directory where the project file resides). It will be opened automatically when the project is opened in the IDE. This useful when preparing samples, projects that will be used by other users or just for yourself - to remind you some important things about the project at a later time.

  8. Default compile-time script. Select a default CTS for the project. It is like the any file attached CTS but it is convenient to specify it here if most of the files in the project will use the same script. If the script has a configuration it will be one for all the files processed by the script.

  9. Apply to. Dialog that helps to assign the default CTS selected to many files in the project - by name, processing option or something else.

  10. Compiler variables. Specify the global compiler variables here - the variables defined for the entire project and available for all the CTS scripts in it (embedded and attached). This depends on the CTS used in the project. Check their documentations for the global variables they may need. For example they could use a global variable to specify an SQL query, file name or some other option.

  11. Compile time script global directory. It is recommended to not change this box. If your change caused problems clear the text in it and click ok - the default value will be set. In some cases you may need to change the global directory where the scripts specified as /somedirectory/.../somescript.vbs are searched. This field specifies the root directory. Copyright 2001-2006 newObjects [ ]