dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separatorAutomation Builderdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorReference: User Interface dl-breadcrumb-item__separatorMenu Commands dl-breadcrumb-item__separatorFile dl-breadcrumb-item__separatorCommand: Save Project as
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Command: Save Project as

The command opens the standard Windows dialog for saving a file. The project can be saved with the desired location and file type.

“File type”

For both ordinary projects and library projects, this list box contains the respective versions of the development system for which the project can be saved. If the current project contains add-ons which are not available in the selected memory format (profile), then the “Extend Profile” dialog opens.

  • “Project files (CODESYS V<version>) (*.project)”: The project is saved as a CODESYS project file named "<project name>.project" for the version of the development system which is currently used or selected.

  • “Library files (V<version>) (*.library)” CODESYS: The project is saved as a CODESYS library file named "<project name>.library" for the version of the development system which is currently used or selected.

If you want to open the project later in an older version, then it makes sense to save for precisely this version, as you will then be immediately notified about possible data loss.

Before you save a project as a library:

  • Make sure that the rules for creating libraries have been followed.

  • If it is to be possible to configure global constants provided by the library at a later time in an application, then you have to define them in a parameter list. A parameter list is a special type of global variable list.

  • When you save the project, no automatic check for errors is performed.

  • Different from CODESYS V2.3 Gateway Server, there is no distinction between "external" and "internal" libraries. Now, in the properties of each individual project object, you can define whether or not the object should be treated as "external".

  • Think about whether the created library should be immediately installed in the system library repository. If so, then use the “Save Project and Install in the Library Repository” command.

  • If you want to protect the library project from later changes, then set the “Released” attribute in the “Project Information” dialog. When the next attempt is made to save the project, a corresponding message will be displayed and the user will have to react to the write protection with deliberate actions.

  • If you save the project as a version of the development system other than the one which is currently used, then you will first be notified about possible data loss.

  • Dialog: Extend Profile