Page History

To edit code, follow the steps below:

Go to Scripts → CodeEditor.

1. Access Scripts → Code Editor. The Code Editor environment displays the contents of the last selected Script Task or Script Class.
2. Select the task or class you want to edit from

From

1. the drop-down list in the main toolbar

, select the task or class you want to edit. To create a new task or class, see Scripts Tasks Configurations or Scripts Classes Configurations earlier on this page.

1. . See the Script Tasks or Script Classes pages for more details on creating tasks or classes.
2. Select the Language in the toolbar.
3. Edit the code.

If needed, select a different code language from the code editor toolbar. 

1. You can also format your code

to be more readable. To do so, click Auto Format. A prompt will appear; click OK.

Click Save.

When Selecting Scripts → CodeEditor,  the Code Editor environment is displayed with the contents of the last selected Script Task or Script Class.

While in that environment, you can change the task or class you are editing using the ComboBox at the top area.

Scripts Compilation

The Scripts Compilation utilizes an incremental compilation approach, which means that scripts are automatically compiled in the background as they are created or modified without requiring explicit user intervention. This approach ensures that only the necessary scripts are compiled, resulting in improved performance and reduced compilation time.

When a script is created or modified, the incremental compilation mechanism identifies the affected scripts and compiles them individually rather than recompiling the entire project. This targeted compilation minimizes the overhead associated with compiling unchanged scripts, resulting in faster build times.

Before deploying a project into a production environment, it is highly recommended to execute a build operation. This build operation ensures that all scripts are up-to-date and compiled correctly, reducing the chances of runtime errors or unexpected behavior.

Productivity Enhancements

1. for readability by clicking Auto Format.
2. Click the floppy disk icon on the toolbar to save the changes.

The image below illustrates the process described above.

Image Added

Productivity Tools

The Scripts Modules offers tools to enhance your productivity when creating and editing scripts. The are as follow:

• IntelliSense: This is IntelliSense: it is a code-completion aid that features listing the available properties and methods for the objects and auto-completing their names.  Additionally In addition to the Properties and Methods of the .NET Framework, it also supports all Project project entities, like Tags tags and Displaysdisplays. Just type Type a dot "(." ) after an element to show its available properties.

• The Toolkit namespaceNamespace: our The platform exposes many .NET libraries to the applicationsolution, but there are a few methods that are frequently required, such as type conversion, copying tags to DataTables and .NET objects, or dynamically changing the communication settings, and others. Those methods are included in a library toolkit. To use these methods, you need to put use then insert TK. in the code editor. , IntelliSense will respond with a list of all available methods and provide a summary documentation for any method you select. Example: double x = See the example below:
  

  Code Block
  double x = TK.ConvertTo<double>("123");

  Access the namespace T.Toolkit.TK class at the Namespaces API to see the list of all methods available.

Scripts Compilation

The Scripts Compilation utilizes an incremental compilation approach, which means that scripts are automatically compiled in the background as they are created or modified without requiring explicit user intervention. This approach ensures that only the necessary scripts are compiled, resulting in improved performance and reduced compilation time. When a script is created or modified, the incremental compilation mechanism identifies the affected scripts and compiles them individually rather than recompiling the entire project. This targeted compilation minimizes the overhead of compiling unchanged scripts, resulting in faster build times.

When you use the code editor, the system constantly compiles code in the background.  We recommend executing a build operation before deploying a project into a production environment. This build operation ensures that all scripts are up-to-date and compiled correctly, reducing the chances of runtime errors or unexpected behavior. For more information, see the Build and Publish page.

The platform has an integrated .NET code debugger. In order to use it, the local computer must have a cache with the necessary files to run the debugger. The steps to enable the debugger are:

• Enable the Debug Information on Runtime → Build and Publish.

• As necessary, save the source code you want to debug. This will create the debug information. This step is only necessary the first time you open the project on the computer. Afterwards, the background compiling generates the necessary debugging information to enable the use of breakpoints and step execution.

Attaching the .NET debugger

In order to have a .NET debugging session, the engineering environment must be connected to the runtime , and the .NET debugger must be attached to server or client process. Follow these steps.

• When Running the projectsolution, go to Runtime → Startup and enable the connect check box.

• If the project solution is already running, go to Runtime → Startup, according to the runtime you want to attach, and connect to the runtime system by pressing the connect button on those pages.

• Open any script that has debugging information and press the Attach .NET debugger button. A message on the bottom of the engineering workspace will show that a debugging session is active with the server components or the client components of the running project.

• When the .NET debugger is attached, the system will stop on the defined breakpoints and will stop automatically when any .NET Exception occurs.