Wiki source code of nuget-feed
Version 37.1 by Gideon Lombard on 2023/09/18 12:20
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 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 | ||
| 4 | |||
| 5 | [[image:1657111373296-938.png]] | ||
| 6 | |||
| 7 | Click the copy icons to copy the text | ||
| 8 | |||
| 9 | [[image:1657111476063-780.png]] | ||
| 10 | |||
| 11 | |||
| 12 | Open Windows Powershell ISE as administrator and click the new button and paste the text in the script window | ||
| 13 | |||
| 14 | [[image:1657111556824-350.png]] | ||
| 15 | |||
| 16 | |||
| 17 | [[image:1657111596157-325.png]] | ||
| 18 | |||
| 19 | Click the Run button to execute the script | ||
| 20 | |||
| 21 | |||
| 22 | ))) | ||
| 23 | 1. ((( | ||
| 24 | For the Visual Studio development users they require to run the following inside a Visual Studio Command Shell as an administrator | ||
| 25 | |||
| 26 | dotnet nuget add source https:~/~/pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json ~-~-name ebs-dev | ||
| 27 | ))) | ||
| 28 | |||
| 29 | 1. | ||
| 30 | |||
| 31 | 1. | ||
| 32 | |||
| 33 | Also while we in the transition phase it might be helpful to add this link via this command: | ||
| 34 | |||
| 35 | >mklink /D c:\dev\src\Packages C:\dev\Packages | ||
| 36 | |||
| 37 | |||
| 38 | [[image:1657115475686-934.png]] | ||
| 39 | |||
| 40 | |||
| 41 | The URL's for different repositories to clone is as follows: | ||
| 42 | |||
| 43 | ~-~-> Application Source Code | ||
| 44 | |||
| 45 | [[image:1657115603808-846.png]] | ||
| 46 | |||
| 47 | |||
| 48 | [[image:1657115842929-756.png]] | ||
| 49 | |||
| 50 | For reference attached is the mappings of the new folders from old folders. | ||
| 51 | |||
| 52 | |||
| 53 | If you want to start making changes follow the following process: | ||
| 54 | |||
| 55 | |||
| 56 | 1. ((( | ||
| 57 | Right click the migration folder and create a new branch via the TortoiseGit menu | ||
| 58 | |||
| 59 | |||
| 60 | 1. [[image:image-20220706143954-1.png]] | ||
| 61 | ))) | ||
| 62 | 1. specify branch name follow this pattern for now (names cannot have spaces use dashes -): | ||
| 63 | |||
| 64 | 1. feature/il-12345 | ||
| 65 | 11. if it is issue log related you can add a -short-description if needed | ||
| 66 | 11. 12345 = replace with issue log number | ||
| 67 | 1. feature/12345 | ||
| 68 | 11. if it is azure task related | ||
| 69 | 11. 12345 = replace with az workitem number | ||
| 70 | 1. feature/short-description | ||
| 71 | 11. if it has no work item associated to it | ||
| 72 | |||
| 73 | 1. make sure you select branch = master and switch to new branch is checked | ||
| 74 | 11. [[image:image-20220706143954-2.png]] | ||
| 75 | |||
| 76 | 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//. | ||
| 77 | |||
| 78 | |||
| 79 | As always please reach out if you get stuck. | ||
| 80 | |||
| 81 | |||
| 82 | Regards |