Once the extension is created, Integration Studio automatically generates, according to the definition of the extension elements, the necessary template files for the development boot-strap of that extension. Once these templates are generated, the source files listed below are added as resources of your extension and you can start coding the behavior of your extension actions.
Template files are the files needed to generate the extension assembly without any custom code, without any code written by the developer. These files are implicitly generated by Integration Studio in the following operations: Create a new Extension, Update the Extension Source Code, or Compare with Template.
The extension source files are stored in the file system in the
Extension folder, under the Source folder in the corresponding sub-folder. You can check them in the Resources tree.
.NET Source files
By default, your extension has the following source files, stored under the
Project files called
Extension implementation files:
Actions are implemented in the
<ExtensionName>.csfile, which contains a .NET method for each action defined by your extension: the method name is
Mss<ActionName>and parameters names are
This file contains the signature of the methods that correspond to the actions exposed by your extension. You must not change these signatures. Any action, either defined in Integration Studio or imported from an assembly, must be defined in this file.
Actions are declared in the
Interface.csfile in the same way as explained above for
Entities are declared in the Entities.cs file, which contains a .NET structure for each entity defined in by your extension: the structure name is
EN<EntityName>EntityRecordand member names are
Record Lists are declared in the
RecordLists.csfile, which contains a .NET class for each record list definition used in your actions: the class name is
RL<RecordListDefinition>RecordListand a set of methods are generated to manage the record list.
Records are declared in the Record.cs file, which contains a .NET structure for each record definition used in your actions: the structure name is
RC<RecordDefinition>Recordand a set of methods are generated to manage the record.
Structures are declared in the
Structures.csfile, which contains a .NET structure for each structure defined in your extension: the structure name is
ST<EntityName>Structureand member names are
These files are automatically generated by Integration Studio, during the Update Source Code operation, and you should not change them in the IDE (Integrated Development Environment).
Bin2folder contains the DLL files associated with your extension and their dependencies, namely: the
OutSystems.Nss<ExtensionName>.dllwhich is the main DLL of your extension; the
OutSystems.HubEdition.RuntimePlatform.dll, which is an internal DLL necessary to Integration Studio.
Objfolder contains the temporary files required by the IDE for building the .NET solution.
Properties of the Source Files
The extension source files are added as resources of the extension with the following properties:
- Name: Name of the resource as explained above.
- Last Modified: Date and time when the resource was last modified since the last save.
- Deploy Action: For the files stored under the
Binariesfolder, this property has the value
Copy to Binaries directory. For the rest of the files, this property has the value
For more information about the Deploy Action property, see Resource Properties.