Wiki source code of getting-started
Version 37.1 by Gideon Lombard on 2023/09/18 12:29
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
5.1 | 1 | Hi Team |
| |
2.1 | 2 | |
| |
5.1 | 3 | |
| |
34.1 | 4 | When you open the projects from the new locations you might have to fix some of the references due to the folder structures changing ie code is not under a "Development" folder as it now is branch based. This can be done by editing the csproj directly or doing a search and replace with the new paths where applicable, alternatively you can remove the old references via IDE and relink to new paths **do not link to old paths on your machine**. |
| |
31.1 | 5 | |
| |
35.1 | 6 | **Prerequisites** |
| |
31.1 | 7 | |
| |
35.1 | 8 | 1. Install [[WinMerge>>https://winmerge.org/]] |
| 9 | 1. Install [[Notepad++>>https://notepad-plus-plus.org/]] | ||
| 10 | 1. Install [[VisualStudio 2022>>https://visualstudio.microsoft.com/vs/]] | ||
| 11 | 1. Install [[VisualStudio Code>>https://code.visualstudio.com/Download]] | ||
| 12 | |||
| 13 | **Source control installation** | ||
| 14 | |||
| 15 | 1. Install [[Git for Windows>>doc:technical-documentation.Source Control.client-tools.git-for-windows.WebHome]] | ||
| 16 | 1. Install [[tortoisegit>>doc:technical-documentation.Source Control.client-tools.tortoisegit.WebHome]] | ||
| |
37.1 | 17 | 1. Setup the [[nuget>>doc:technical-documentation.Source Control.client-tools.nuget-feed.WebHome]] feed |
| |
35.1 | 18 | |
| |
31.1 | 19 | |
| |
2.1 | 20 | Also while we in the transition phase it might be helpful to add this link via this command: |
| 21 | |||
| 22 | >mklink /D c:\dev\src\Packages C:\dev\Packages | ||
| 23 | |||
| 24 | |||
| |
29.1 | 25 | [[image:1657115475686-934.png]] |
| |
2.1 | 26 | |
| |
29.1 | 27 | |
| 28 | The URL's for different repositories to clone is as follows: | ||
| 29 | |||
| 30 | ~-~-> Application Source Code | ||
| 31 | |||
| 32 | [[image:1657115603808-846.png]] | ||
| 33 | |||
| 34 | |||
| 35 | [[image:1657115842929-756.png]] | ||
| 36 | |||
| |
2.1 | 37 | For reference attached is the mappings of the new folders from old folders. |
| 38 | |||
| 39 | |||
| 40 | If you want to start making changes follow the following process: | ||
| 41 | |||
| 42 | |||
| 43 | 1. ((( | ||
| 44 | Right click the migration folder and create a new branch via the TortoiseGit menu | ||
| 45 | |||
| 46 | |||
| |
5.1 | 47 | 1. [[image:image-20220706143954-1.png]] |
| |
2.1 | 48 | ))) |
| 49 | 1. specify branch name follow this pattern for now (names cannot have spaces use dashes -): | ||
| 50 | |||
| 51 | 1. feature/il-12345 | ||
| 52 | 11. if it is issue log related you can add a -short-description if needed | ||
| 53 | 11. 12345 = replace with issue log number | ||
| 54 | 1. feature/12345 | ||
| 55 | 11. if it is azure task related | ||
| 56 | 11. 12345 = replace with az workitem number | ||
| 57 | 1. feature/short-description | ||
| 58 | 11. if it has no work item associated to it | ||
| 59 | |||
| 60 | 1. make sure you select branch = master and switch to new branch is checked | ||
| |
5.1 | 61 | 11. [[image:image-20220706143954-2.png]] |
| |
2.1 | 62 | |
| 63 | As mentioned Friday if there is a piece of new code that has sync over yet and you need it, merge it over on your end with something like winmerge //once you have created a feature branch//. | ||
| 64 | |||
| 65 | |||
| 66 | As always please reach out if you get stuck. | ||
| 67 | |||
| 68 | |||
| |
5.1 | 69 | Regards |