Changes for page nuget-feed

Last modified by Mohamed Varachia on 2024/02/05 14:37
<
From version < 39.1 >
edited by Gideon Lombard
on 2023/09/18 12:24
To version < 35.1 >
edited by Gideon Lombard
on 2023/09/15 09:39
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

Need help?

If you need help with XWiki you can contact: