Changes for page getting-started

Last modified by Douglas Wait on 2026/07/09 06:52

<
From version < 37.1 >
edited by Gideon Lombard
on 2023/09/18 12:29
To version < 12.1 >
edited by Gideon Lombard
on 2022/07/06 12:54
>
Change comment: Uploaded new attachment "1657112070557-484.png", version {1}

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -technical-documentation.Source Control.WebHome
1 +Technical Documentation.Source Control.WebHome
Content
... ... @@ -3,37 +3,47 @@
3 3  
4 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 5  
6 -**Prerequisites**
7 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]]
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:
12 12  
13 -**Source control installation**
9 +1. make sure your VS is updated with the latest updates (critical)
10 +1. (((
11 +install [[The Azure Artifacts Credential Provider>>url:https://github.com/Microsoft/artifacts-credprovider#setup]] and select the **PowerShell helper script **link
14 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 -1. Setup the [[nuget>>doc:technical-documentation.Source Control.client-tools.nuget-feed.WebHome]] feed
13 +[[image:1657111373296-938.png]]
18 18  
15 +Click the copy icons to copy the text
19 19  
20 -Also while we in the transition phase it might be helpful to add this link via this command:
17 +[[image:1657111476063-780.png]]
21 21  
22 ->mklink /D c:\dev\src\Packages C:\dev\Packages
23 23  
20 +Open Windows Powershell ISE as administrator and click the new button and paste the text in the script window
24 24  
25 -[[image:1657115475686-934.png]]
22 +[[image:1657111556824-350.png]]
26 26  
27 27  
28 -The URL's for different repositories to clone is as follows:
25 +[[image:1657111596157-325.png]]
29 29  
30 - ~-~-> Application Source Code
27 +Click the Run button to execute the script
31 31  
32 -[[image:1657115603808-846.png]]
29 +
30 +)))
31 +1. (((
32 +For the Visual Studio development users they require to run the following inside a Visual Studio Command Shell as an administrator
33 33  
34 +dotnet nuget add source https:~/~/pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json ~-~-name ebs-dev
35 +)))
34 34  
35 -[[image:1657115842929-756.png]]
37 +1.
36 36  
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 +
37 37  For reference attached is the mappings of the new folders from old folders.
38 38  
39 39  
... ... @@ -60,6 +60,7 @@
60 60  1. make sure you select branch = master and switch to new branch is checked
61 61  11. [[image:image-20220706143954-2.png]]
62 62  
73 +
63 63  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//.
64 64  
65 65  
1657114851784-392.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -32.1 KB
Content
1657114877100-308.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -45.2 KB
Content
1657114930282-807.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -34.8 KB
Content
1657114946064-403.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
1657114967427-838.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -51.4 KB
Content
1657114979552-688.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -34.8 KB
Content
1657114991695-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -38.3 KB
Content
1657115030668-697.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -50.5 KB
Content
1657115041449-256.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -51.4 KB
Content
1657115057201-480.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
1657115066593-304.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
1657115075687-171.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
1657115106191-233.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -38.9 KB
Content
1657115475686-934.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -17.0 KB
Content
1657115603808-846.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -47.5 KB
Content
1657115842929-756.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.gideonl
Size
... ... @@ -1,1 +1,0 @@
1 -42.4 KB
Content

Need help?

If you need help with XWiki you can contact: