Command 'Save Project as'

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

“File type”

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

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

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

Before saving 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 must define them in a parameter list. A parameter list is a special type of global variable list.
When saving the project, no automatic check for errors is performed.
Unlike CoDeSys V2.3, there is no distinction between 'external' and 'internal' libraries. Now you can define in the properties of each individual project object whether or not it should be treated as 'external'.
Consider whether the library created is to be installed in the system library repository immediately. If so, then use the command 'Save project and install in the library repository'.
If you want to protect the library project from later changes, then set the “Released” attribute in the “Project Information” dialog box. At the next attempt to save the project, a corresponding message will be displayed and the user must respond to the write protection with deliberate actions.
If you save the project as a version of the development system other than the one currently in use, then you will be informed first about possible data loss.

Dialog box 'Extend Profile'

In this dialog box, the selected profile (memory format) can be extended by the add-ons that are contained in the current project. The profile is saved temporarily and then deleted after being saved or exported.

“Add to profile”	: The current profile is extended by the add-on so that the add-on data of the current project is also saved.
“Add-on”	The add-on of the current project that is not contained in the selected memory format.
“Version”	Version of the “Add-on” included in the current profile. If several versions are installed, then the version can be selected.
“Save profile”	Opens the “Enter Profile Name” dialog box. In this dialog box, specify the name for the new profile. The new profile is saved permanently at `‎$ProgramData$/$PRODUCT$/CustomInformationalProfiles‎`.
“Use saved profile”	The profile which was permanently saved in “Save profile” is used for saving or exporting the current project.