Changes for page nuget-feed

Last modified by Mohamed Varachia on 2024/02/05 14:37
<
From version < 18.1 >
edited by Gideon Lombard
on 2022/07/06 13:42
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,14 +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 your VS is updated with the latest updates (critical)
1 +1. Make sure your VS is updated with the latest updates (critical)
10 10  1. (((
11 -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
12 12  
13 13  [[image:1657111373296-938.png]]
14 14  
... ... @@ -24,57 +24,10 @@
24 24  
25 25  [[image:1657111596157-325.png]]
26 26  
27 -Click the Run button to execute the script
28 -
29 -
19 +Click the Run button to execute the script.
30 30  )))
31 31  1. (((
32 -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.
33 33  
34 34  dotnet nuget add source https:~/~/pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json ~-~-name ebs-dev
35 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
1657114991695-101.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.gideonl
Size
... ... @@ -1,0 +1,1 @@
1 +38.3 KB
Content
1657115030668-697.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.gideonl
Size
... ... @@ -1,0 +1,1 @@
1 +50.5 KB
Content
1657115041449-256.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.gideonl
Size
... ... @@ -1,0 +1,1 @@
1 +51.4 KB
Content
1657115057201-480.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.gideonl
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
1657115066593-304.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.gideonl
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
1657115075687-171.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.gideonl
Size
... ... @@ -1,0 +1,1 @@
1 +37.6 KB
Content
1657115106191-233.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.gideonl
Size
... ... @@ -1,0 +1,1 @@
1 +38.9 KB
Content
1657115475686-934.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.gideonl
Size
... ... @@ -1,0 +1,1 @@
1 +17.0 KB
Content
1657115603808-846.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.gideonl
Size
... ... @@ -1,0 +1,1 @@
1 +47.5 KB
Content
1657115842929-756.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.gideonl
Size
... ... @@ -1,0 +1,1 @@
1 +42.4 KB
Content

Applications

Navigation

Need help?

If you need help with XWiki you can contact: