Wiki source code of getting-started

Version 33.1 by Gideon Lombard on 2023/09/15 09:30
Show last authors
1 Hi Team
2
3 **Pre-requisites**
4
5 ~1. Install [[WinMerge>>https://winmerge.org/]]
6
7 2. Install [[Notepad++>>https://notepad-plus-plus.org/]]
8
9 3. Install [[VisualStudio Code>>https://code.visualstudio.com/Download]]
10
11 4. Install [[Visual Studio 2022>>https://visualstudio.microsoft.com/vs/]]
12
13 **Software Installation**
14
15 ~1. Install [[Git for Windows>>doc:technical-documentation.Source Control.client-tools.git-for-windows.WebHome]]
16
17 2. Install [[tortoisegit>>doc:technical-documentation.Source Control.client-tools.tortoisegit.WebHome]]
18
19 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**​.
20
21
22 Some of the projects have been converted to start using our own nuget feed so to ensure you do not have any connectivity issues:1.
23
24
25
26 1. make sure your VS is updated with the latest updates (critical)
27 1. (((
28 install [[The Azure Artifacts Credential Provider>>url:https://github.com/Microsoft/artifacts-credprovider#setup]] and select the **PowerShell helper script **link
29
30 [[image:1657111373296-938.png]]
31
32 Click the copy icons to copy the text
33
34 [[image:1657111476063-780.png]]
35
36
37 Open Windows Powershell ISE as administrator and click the new button and paste the text in the script window
38
39 [[image:1657111556824-350.png]]
40
41
42 [[image:1657111596157-325.png]]
43
44 Click the Run button to execute the script
45
46
47 )))
48 1. (((
49 For the Visual Studio development users they require to run the following inside a Visual Studio Command Shell as an administrator
50
51 dotnet nuget add source https:~/~/pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json ~-~-name ebs-dev
52 )))
53
54 1.
55
56 1.
57
58 Also while we in the transition phase it might be helpful to add this link via this command:
59
60 >mklink /D c:\dev\src\Packages C:\dev\Packages
61
62
63 [[image:1657115475686-934.png]]
64
65
66 The URL's for different repositories to clone is as follows:
67
68 ~-~-> Application Source Code
69
70 [[image:1657115603808-846.png]]
71
72
73 [[image:1657115842929-756.png]]
74
75 For reference attached is the mappings of the new folders from old folders.
76
77
78 If you want to start making changes follow the following process:
79
80
81 1. (((
82 Right click the migration folder and create a new branch via the TortoiseGit menu
83
84
85 1. [[image:image-20220706143954-1.png]]
86 )))
87 1. specify branch name follow this pattern for now (names cannot have spaces use dashes -):
88
89 1. feature/il-12345
90 11. if it is issue log related you can add a -short-description if needed
91 11. 12345 = replace with issue log number
92 1. feature/12345
93 11. if it is azure task related
94 11. 12345 = replace with az workitem number
95 1. feature/short-description
96 11. if it has no work item associated to it
97
98 1. make sure you select branch = master and switch to new branch is checked
99 11. [[image:image-20220706143954-2.png]]
100
101 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//.
102
103
104 As always please reach out if you get stuck.
105
106
107 Regards

Applications

Navigation

Need help?

If you need help with XWiki you can contact: