Changing Version Control to Visual Studio

How to change the version control software from Sourcetree to the inherent system on Visual Studio

Difficulté

Hard Difficile

Durée

1 hour(s) heure(s)

Visual Studio, Source, Version TcAeShell_Icons.jpg

Introduction

In March 2022 the password policy of the system behind SourceTree / Bitbucket and Atlassian changed - link. This meant all machine would need a complex password login change for the SourceTree program used for version control of the PLC code.

This was not straight-forward to resolve, so the decision was made to change the version control system to the one that is packaged with the Visual Studio system by default. This is a better method anyway, but it needs the "TcXaeShell" installed.

...The TcXaeShell is simply a newer version of Visual Studio that includes Source control, rebadged for TwinCAT3

Étape 1 - Ensure TcXAEShell is installed

1. Right click on TwinCAT service in the task bar
2. If TcXaeShell is installed you will see the gold Icon with the cog inside

There is a Visual Studio icon here instead, you will need to install TcXaeShell. Ask one of the IT team to connect and download it

...It is over 1Gb long!

G:\Design\TwinCAT3\TC31-FULL-Setup.3.1.4024.22.exe

Étape 2 - Open TwinCAT Shell

Étape 3 - Open the Machine Solution File

Étape 4 - Create the Repository

1. Open Team Explorer
2. Clone a new Git Repository
3. URL to clone: https://bitbucket.org/StugaMachinery/tc3Multi
4. Click on the destination setup
5. Create a new folder under the machine build folder called "source"
6. Click 'Clone'

Étape 5 - Move The PLC_Reset Project

Étape 6 - Delete the versionControl Folder

Delete the versionControl folder completely

...This prevents confusion in the future of where the project exists

Étape 7 - Update Control Systems Log

Update the Version Control column on the board to "VisualStudio" to log the completion of this task

en none 0 Draft