Changes for page nuget-feed
Last modified by Mohamed Varachia on 2024/02/05 14:37
Change comment:
There is no comment for this version
Summary
-
Page properties (4 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 3 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - nuget-feed1 +getting-started - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -technical-documentation.Source Control. client-tools.WebHome1 +technical-documentation.Source Control.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. mohamedv1 +XWiki.gideonl - Content
-
... ... @@ -1,27 +1,105 @@ 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 1 +Hi Team 4 4 5 - [[image:image-20240205162643-1.png]]3 +**Pre-requisites** 6 6 7 - 3.Click onhighlighted link5 +~1. Install [[WinMerge>>https://winmerge.org/]] 8 8 9 -[[ image:image-20240205163118-3.png]]7 +2. Install [[Notepad++>>https://notepad-plus-plus.org/]] 10 10 11 - 4. Copycodefrom Github9 +3. Install [[VisualStudio Code>>https://code.visualstudio.com/Download]] 12 12 11 +4. Install [[Visual Studio 2022>>https://visualstudio.microsoft.com/vs/]] 13 13 13 +**Software Installation** 14 14 15 - 5.Open Windows PowershellISE as administrator and clickthe new button and paste the text in the script window15 +~1. Install 16 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 +Open Windows Powershell ISE as administrator and click the new button and paste the text in the script window 36 + 17 17 [[image:1657111556824-350.png]] 18 18 19 19 20 20 [[image:1657111596157-325.png]] 21 21 22 - 6.Click the Run button to execute the script.42 +Click the Run button to execute the script 23 23 24 -7. For the Visual Studio development user they need to run the following inside a Visual Studio Command Shell as an administrator. 44 + 45 +))) 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 25 26 - **dotnet nuget add source https:~/~/pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json ~-~-name ebs-dev**49 +dotnet nuget add source https:~/~/pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json ~-~-name ebs-dev 27 27 ))) 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,1 +1,0 @@ 1 -XWiki.mohamedv - Size
-
... ... @@ -1,1 +1,0 @@ 1 -108.9 KB - Content
- image-20240205162823-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.mohamedv - Size
-
... ... @@ -1,1 +1,0 @@ 1 -123.0 KB - Content
- image-20240205163118-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.mohamedv - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.3 KB - Content