Changes for page nuget-feed

Last modified by Mohamed Varachia on 2024/02/05 14:37

<
From version < 30.1 >
edited by Gideon Lombard
on 2023/09/15 09:21
To version < 39.1 >
edited by Gideon Lombard
on 2023/09/18 12:24
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -getting-started
1 +nuget-feed
Parent
... ... @@ -1,1 +1,1 @@
1 -technical-documentation.Source Control.WebHome
1 +technical-documentation.Source Control.client-tools.WebHome
Content
... ... @@ -1,60 +1,6 @@
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 that you download and install the latest version of Git from [[https:~~/~~/gitforwindows.org/>>https://gitforwindows.org/]]
10 -
11 -
12 -[[image:1657114851784-392.png]]
13 -
14 -
15 -Leave all settings as per default on this screen.
16 -
17 -[[image:1657114877100-308.png]]
18 -
19 -
20 -[[image:1657114930282-807.png]]
21 -
22 -
23 -[[image:1657114946064-403.png]]
24 -
25 -
26 -
27 -[[image:1657114967427-838.png]]
28 -
29 -[[image:1657114979552-688.png]]
30 -
31 -
32 -[[image:1657114991695-101.png]]
33 -
34 -
35 -[[image:1657115030668-697.png]]
36 -
37 -[[image:1657115041449-256.png]]
38 -
39 -
40 -[[image:1657115057201-480.png]]
41 -
42 -
43 -[[image:1657115066593-304.png]]
44 -
45 -
46 -[[image:1657115075687-171.png]]
47 -
48 -
49 -[[image:1657115106191-233.png]]
50 -
51 -
52 -
53 -
54 -
55 -1. make sure your VS is updated with the latest updates (critical)
1 +1. Make sure your VS is updated with the latest updates (critical)
56 56  1. (((
57 -install [[The Azure Artifacts Credential Provider>>url:https://github.com/Microsoft/artifacts-credprovider#setup]] and select the **PowerShell helper script **link
3 +Install [[The Azure Artifacts Credential Provider>>url:https://github.com/Microsoft/artifacts-credprovider#setup]] and select the **PowerShell helper script **link
58 58  
59 59  [[image:1657111373296-938.png]]
60 60  
... ... @@ -70,67 +70,10 @@
70 70  
71 71  [[image:1657111596157-325.png]]
72 72  
73 -Click the Run button to execute the script
74 -
75 -
19 +Click the Run button to execute the script.
76 76  )))
77 77  1. (((
78 -For the Visual Studio development users they require to run the following inside a Visual Studio Command Shell as an administrator
22 +For the Visual Studio development user they need to run the following inside a Visual Studio Command Shell as an administrator.
79 79  
80 80  dotnet nuget add source https:~/~/pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json ~-~-name ebs-dev
81 81  )))
82 -
83 -1.
84 -
85 -1.
86 -
87 -Also while we in the transition phase it might be helpful to add this link via this command:
88 -
89 ->mklink /D c:\dev\src\Packages C:\dev\Packages
90 -
91 -
92 -[[image:1657115475686-934.png]]
93 -
94 -
95 -The URL's for different repositories to clone is as follows:
96 -
97 - ~-~-> Application Source Code
98 -
99 -[[image:1657115603808-846.png]]
100 -
101 -
102 -[[image:1657115842929-756.png]]
103 -
104 -For reference attached is the mappings of the new folders from old folders.
105 -
106 -
107 -If you want to start making changes follow the following process:
108 -
109 -
110 -1. (((
111 -Right click the migration folder and create a new branch via the TortoiseGit menu
112 -
113 -
114 -1. [[image:image-20220706143954-1.png]]
115 -)))
116 -1. specify branch name follow this pattern for now (names cannot have spaces use dashes -):
117 -
118 -1. feature/il-12345
119 -11. if it is issue log related you can add a -short-description if needed
120 -11. 12345 = replace with issue log number
121 -1. feature/12345
122 -11. if it is azure task related
123 -11. 12345 = replace with az workitem number
124 -1. feature/short-description
125 -11. if it has no work item associated to it
126 -
127 -1. make sure you select branch = master and switch to new branch is checked
128 -11. [[image:image-20220706143954-2.png]]
129 -
130 -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//.
131 -
132 -
133 -As always please reach out if you get stuck.
134 -
135 -
136 -Regards

Need help?

If you need help with XWiki you can contact: