Changes for page nuget-feed

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

Applications

Navigation

Need help?

If you need help with XWiki you can contact: