Project file encryption

	Secure protection only with encryption of the project file The project file must be encrypted in any case when using encryption, because it contains important information about the properties of the project. Manipulation of this information could prevent secure encryption of the source code.

	Make an unencrypted backup before encrypting! Before encrypting a project: always make a backup of the project in its unencrypted state!

The encryption of the project file is set via the TwinCAT project node.

The project is linked to a user database.

1. Select the TwinCAT project node in the project tree in the Solution Explorer.

2. Select the command Encrypt Project File in the context menu.

In the Properties view, the value of the EncryptFile property in the Security category is set to TRUE.
Project file encryption 3:

The project file is encrypted. It contains information on the components of the solution. On setting the encryption the project file itself is now encrypted. The encryption is not inherited to the components contained in the project. The encryption must be set individually for all (main) components of the project.

	Only valid for TwinCAT 3.1 Build 4024.0: creation of a User DB requires Crypto Version 1 In the TwinCAT version Build 4024.0, a user database for the TwinCAT Software Protection may only be created with an OEM certificate with Crypto version 1!