|
|
|
|
|
|
|
|
|
|
- Overview
- Before changing version
- When changing version
- The change of version
- Working with the branch
SCM: Project version changes
When several projects share elements in the same SCM, version changes of WINDEV, WEBDEV and WINDEV Mobile projects must be made with care to avoid blocking one of the projects. As soon as a project is opened in a later version of WINDEV, WEBDEV or WINDEV Mobile (e.g. from version 28 to version 2024), all its elements (windows, classes, etc.) are "converted" to the new format to take account of the version's new features. If some of these elements are shared with other projects via SCM, the other projects (still in earlier version, 28 for example) will not be able to retrieve the update of elements opened with a later version. Local projects in version 28 would still run, but if they were not upgraded and one of their elements is opened with the latest version, changes can no longer be easily retrieved. Make a list of the projects that share elements via the SCM: If you choose to open a project with a new version, all projects that share at least one element will have to be opened with that version at the same time. For each shared element found in the "main" project, list all the projects that share this element.
Note: In the SCM administrator, a shared element can be identified by a specific icon. To list the projects that share an element: - Start the SCM administrator.
- Open the context menu of the desired element and select "Properties".
- Go to the "Shares" tab.
This operation must be performed recursively for each project sharing an element. If you open a project A with a later version, and this project shares an element with project B, which in turn shares another element with project C, all 3 projects must be upgraded at the same time. Important: Plan a date to upgrade your projects. Upgrading a project with shared elements requires great care. The following operations must be performed: - In the SCM administrator, make sure that all the elements of all relevant projects are checked in. No elements should be checked out before the version change.
- Open the relevant projects in their current version (28 for example) and check whether all the local elements are updated.
These checks are used to make sure that the backup branch that will be created later will contain all the elements in their most updated version.
Furthermore, having a local version of project properly updated is a great benefit in case of problem.
Projects must be upgraded one by one. If you work as part of a team, don't change version simultaneously for the linked projects. First of all, modify the project containing the greatest number of shared elements. For each project: - Open the project in the new version (e.g. 2024). An SCM window appears, indicating that you are trying to open a project from an earlier version.
- Select "Migrate project to new version and keep SCM connection", and don't forget to check "Create branch in the SCM with the old project".
Creating a branch is essential in most cases. - In the branch creation wizard, keep the default branch name ("Backup version XX").
If you modify the name of this branch, don't forget to apply the same branch name to all the projects.
Naming the branch is essential in order for the shares of elements between projects to be properly re-applied within the branch. - At step 3/3 of the branch creation wizard, check "Find and recreate the shares in the branch".
If your local projects are up to date, check "Use local version as reference for the branch". - Once the branch is created and the project opened in a later version, check all the checked-out project elements back in and close the project.
- In the SCM administrator, make sure that all the project elements have been checked back in.
- Also check that the branch containing the old project version ("Backup version XX") is present.
This operation must be performed for all the affected projects. Once all the projects have changed version, you still have the ability to work on the former project version (version 28 for example) if necessary (urgent modification or correction for example). To do so, simply open the project located in the branch: - if the migration was performed on your computer, the branch creation wizard automatically copied the project to "C:\My Projects.Branches\Backup version XX\" (default directory).
- if the migration was performed on another computer or by another developer, select "Open a project from the SCM" and select the project in the following location: "SCM:\\Branches\Backup version XX\" .
Don't forget to define a local path used to indicate that this project version comes from a branch.
After making modifications in a branch, carry them over to the most recent project version (2024, for example). To perform this operation: - Open the project in the latest version.
- On the "SCM" tab, in the "Project" group, expand "Branches" and select "Retrieve modifications from a branch".
- A wizard helps you apply your modifications.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|