]> 2026-05-26T11:08:45+02:00 Changing Version Control to Visual Studio 0 en Draft How to change the version control software from Sourcetree to the inherent system on Visual Studio Hard 1 hour(s) In March 2022 the password policy of the system behind SourceTree / Bitbucket and Atlassian changed - [https://community.atlassian.com/t5/Bitbucket-articles/Announcement-Bitbucket-Cloud-account-password-usage-for-Git-over/ba-p/1948231 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. <div class="icon-instructions info-icon"> <div class="icon-instructions-icon"><i class="fa fa-info-circle"></i></div> <div class="icon-instructions-text">...The TcXaeShell is simply a newer version of Visual Studio that includes Source control, rebadged for TwinCAT3</div> </div> false en TcAeShell_Icons.jpg none Delete the versionControl folder completely <div class="icon-instructions info-icon"> <div class="icon-instructions-icon"><i class="fa fa-info-circle"></i></div> <div class="icon-instructions-text">...This prevents confusion in the future of where the project exists</div> </div><br/> Update the Version Control column on the [https://stugaltd.monday.com/boards/304269981 board] to "VisualStudio" to log the completion of this task #Right click on TwinCAT service in the task bar #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. Procedure is [https://stuga.dokit.app/wiki/Upgrading_Visual_Studio_to_Beckhoff_TCXAEShell here] <br/> #Open Team Explorer #Clone a new Git Repository #URL to clone: https://bitbucket.org/StugaMachinery/tc3Multi #Click on the destination setup #Create a new folder under the machine build folder called "source" #Click 'Clone' [[Archiving a TwinCAT Project]] [[Creating Backup of TwinCAT Mapping]] <br/><div class="icon-instructions caution-icon"> <div class="icon-instructions-icon"><i class="fa fa-exclamation-triangle"></i></div> <div class="icon-instructions-text">...This is really, really important to do</div> </div><br/> Atlassian Username is StugaMachinery Password is stored in the file G:\IT Department\SourceTree BitBucket App Password.txt <div class="icon-instructions info-icon"> <div class="icon-instructions-icon"><i class="fa fa-info-circle"></i></div> <div class="icon-instructions-text">...Sometimes, the password credentials are already stored and the password entry is not necessary</div> </div> #Right click the PLC_Reset Project #Select Change Project #Navigate to the repository you have created in Step 6 c:\TwinCAT\Stuga\BuildNo\source\PLC_Reset\PLC_Reset.plcproj #Repeat for the tc3Multi project If so, this is probably due to the PLC project having no "Instance": # Build the solution # Import the mappings file taken in step 2 <br/><div class="icon-instructions info-icon"> <div class="icon-instructions-icon"><i class="fa fa-info-circle"></i></div> <div class="icon-instructions-text">...The "Instance" is created when the PLC project is built. This has all the IO definitions in it (ie axes, outputArray, inputArray, etc) If it does not exist, the IO cannot be linked. Once built, you can then import the old links back in again</div> </div><br/> Check the PLC Projects are called tc3Multi PLC_Reset If they have a number after them (as in picture, they will need to be '''renamed first''' Open TwinCAT Shell Open the Machine Solution File Delete the versionControl Folder Update Control Systems Log Ensure TcXAEShell is installed Enter Git Credentials (if required) Move The PLC_Reset and tc3Multi Project Take a backup of the current build project Backup the Mappings information Check if the IO links have disappeared Clone the Repository Ensure the PLC Project Names are Compatible Visual Studio Source Version 2022-09-12T12:15:03Z 2459835.0104514 Changing Version Control to Visual Studio 0 false false 0 0 0 1 plainlist 3 [[:Dokit:DocOptions]] [[DokitEPIEnable::yes]] Changing Version Control to Visual Studio# QUERYee7a61aae48f1c3f91d8e4d7736360be