Using Working Copies
Checking out a project
You can copy CODESYS projects, which are saved in the SVN repository, to your development system for editing.
Open CODESYS.
Click
.The Checkout dialog opens.
Specify the URL of the SVN repository and select a project in the SVN repository tree.
A CODESYS project is automatically identified by its file extension (
.project
,_project
,.library
, or_library
) as a "project" or "library project" at checkout.In Checkout to, specify the name and location of the working copy on your development system.
Click OK to exit the dialog.
The project opens in CODESYS. In the object tree of the project, the SVN link is shown with overlaid icons. Now the project is saved as a working copy on your development system.
Editing the working copy
Tip
Update the working copy before you start editing, especially if the project is revised by a team. You prevent conflicts in this way.
Checking for version profile consistency
As of version 4.4.0.0, CODESYS SVN checks whether or not the storage profile of the project (CODESYS version under which the project was saved) in the working copy matches the storage profile in the SVN repository. If the profiles differ, then the note Storage profile update is displayed in red in the Pending Changes view and in the Commit dialog. Moreover, for actions which require commits between the repository and the working copy, a message dialog notifies you about the inconsistency. You get support with the necessary change to the storage profile. For example, this can happen with the following SVN actions: commit, revert, update, and check out.
If the meta.profile object appears changed as , then it also has to be committed because it contains the storage profile information.
Certain actions are no longer possible in the case of different storage profiles at the object level in order to prevent any problems caused by inconsistencies. At the project level, there is at least always the option in the working copy to use the Save Project as command or to adapt the storage format again by reverting to a corresponding revision, even if this can result in minor data losses.
You can see the current storage format of the working copy in the Project Information on the File tab under Saved with.
Open the working copy.
Click
(symbol:).
Your working copy is up to date.
Continue developing your project.
Click
.The dialog opens. There you can browse your changes.
Exit the dialog.
If necessary, you can click CODESYS SVN first checks whether or not the storage profile of the working copy matches the storage profile of the project in the SVN repository. If the storage profiles differ, then the revert cannot be done at the object level (see Note above).
in the context menu. As a result,The file is reverted back to the base revision and your changes are discarded.
If necessary, you can click in the context menu of an edited object.
The compare dialog opens. You can resolve any conflicts here.
Close the compare dialog.
Click
(Symbol).
The Commit dialog opens.
In Message, specify a log entry that describes your changes. Example:
Changes for customer ABC, request 1234.
Your changes are saved in the SVN repository as a revision with a revision number.
Changed working copy format in CODESYS SVN V4.1.0.0 and higher
For projects in version CODESYS SVN V4.1.0.0
and higher, the working directory (working copy) has a new format.
If you open a project that was created with V4.0.4.0
or lower, then the project is updated automatically to the new format when it is opened.
If you open a project that was created with V4.0.4.0
or lower and the project is based on an older SVN version of 1.7.x
or lower, then you are prompted whether or not CODESYS should update the format. If you reject the update, then the SVN link of the project will be deactivated. You can still load and edit the project.
The update does not have an effect on saving to the SVN server. You can also check out projects with earlier versions of the client. The new format affects only the local working directory.
For more information, see: http://svnbook.red-bean.com/en/1.8/svn.ref.svn.c.upgrade.html