Wiki source code of getting-started

Version 14.1 by Gideon Lombard on 2022/07/06 13:41
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
7 Some of the projects have been converted to start using our own nuget feed so to ensure you do not have any connectivity issues:
8
9 1. make sure your VS is updated with the latest updates (critical)
10 1. (((
11 install [[The Azure Artifacts Credential Provider>>url:https://github.com/Microsoft/artifacts-credprovider#setup]] and select the **PowerShell helper script **link
12
13 [[image:1657111373296-938.png]]
14
15 Click the copy icons to copy the text
16
17 [[image:1657111476063-780.png]]
18
19
20 Open Windows Powershell ISE as administrator and click the new button and paste the text in the script window
21
22 [[image:1657111556824-350.png]]
23
24
25 [[image:1657111596157-325.png]]
26
27 Click the Run button to execute the script
28
29
30 )))
31 1. (((
32 For the Visual Studio development users they require to run the following inside a Visual Studio Command Shell as an administrator
33
34 dotnet nuget add source https:~/~/pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json ~-~-name ebs-dev
35 )))
36
37 1.
38
39 1.
40
41 Also while we in the transition phase it might be helpful to add this link via this command:
42
43 >mklink /D c:\dev\src\Packages C:\dev\Packages
44
45
46
47 For reference attached is the mappings of the new folders from old folders.
48
49
50 If you want to start making changes follow the following process:
51
52
53 1. (((
54 Right click the migration folder and create a new branch via the TortoiseGit menu
55
56
57 1. [[image:image-20220706143954-1.png]]
58 )))
59 1. specify branch name follow this pattern for now (names cannot have spaces use dashes -):
60
61 1. feature/il-12345
62 11. if it is issue log related you can add a -short-description if needed
63 11. 12345 = replace with issue log number
64 1. feature/12345
65 11. if it is azure task related
66 11. 12345 = replace with az workitem number
67 1. feature/short-description
68 11. if it has no work item associated to it
69
70 1. make sure you select branch = master and switch to new branch is checked
71 11. [[image:image-20220706143954-2.png]]
72
73
74 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//.
75
76
77 As always please reach out if you get stuck.
78
79
80 Regards