Wiki source code of getting-started

Version 38.1 by Mohamed Varachia on 2024/02/07 10:42

Show last authors
1 Hi Team
2
3
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**​.
5
6 **Prerequisites**
7
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]]
17 1. Setup the [[nuget>>doc:technical-documentation.Source Control.client-tools.nuget-feed.WebHome]] feed
18
19 Also while we in the transition phase it might be helpful to add this link via this command:
20
21 >mklink /D c:\dev\src\Packages C:\dev\Packages
22
23 (% style="font-size:18px" %)clone to here: C:\dev\ebsphere\migration\master
24
25
26 [[image:1657115475686-934.png]]
27
28
29
30 The URL's for different repositories to clone is as follows:
31
32 [[image:image-20240207124136-3.png]]
33
34 ~-~-> Application Source Code
35
36 [[image:1657115603808-846.png]]
37
38
39 [[image:1657115842929-756.png]]
40
41 For reference attached is the mappings of the new folders from old folders.
42
43
44 If you want to start making changes follow the following process:
45
46
47 1. (((
48 Right click the migration folder and create a new branch via the TortoiseGit menu
49
50
51 1. [[image:image-20220706143954-1.png]]
52 )))
53 1. specify branch name follow this pattern for now (names cannot have spaces use dashes -):
54
55 1. feature/il-12345
56 11. if it is issue log related you can add a -short-description if needed
57 11. 12345 = replace with issue log number
58 1. feature/12345
59 11. if it is azure task related
60 11. 12345 = replace with az workitem number
61 1. feature/short-description
62 11. if it has no work item associated to it
63
64 1. make sure you select branch = master and switch to new branch is checked
65 11. [[image:image-20220706143954-2.png]]
66
67 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//.
68
69 As always please reach out if you get stuck.