Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-getting-started
	1	+git-for-windows

Parent

...	...	@@ -1,1 +1,1 @@
1		-xwiki:technical-documentation.Source Control.WebHome
	1	+technical-documentation.Source Control.client-tools.WebHome

Content

...	...	@@ -1,11 +9,3 @@
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	9	~1. Make sure that you download and install the latest version of Git from [[https:~~/~~/gitforwindows.org/>>https://gitforwindows.org/]]
10	10
11	11
...	...	@@ -12,6 +12,8 @@
12	12	[[image:1657114851784-392.png]]
13	13
14	14
	7	+Keep all the options as per the default.
	8	+
15	15	[[image:1657114877100-308.png]]
16	16
17	17
...	...	@@ -45,90 +45,3 @@
45	45
46	46
47	47	[[image:1657115106191-233.png]]
48		-
49		-
50		-
51		-
52		-
53		-1. make sure your VS is updated with the latest updates (critical)
54		-1. (((
55		-install [[The Azure Artifacts Credential Provider>>url:https://github.com/Microsoft/artifacts-credprovider#setup]] and select the **PowerShell helper script **link
56		-
57		-[[image:1657111373296-938.png]]
58		-
59		-Click the copy icons to copy the text
60		-
61		-[[image:1657111476063-780.png]]
62		-
63		-
64		-Open Windows Powershell ISE as administrator and click the new button and paste the text in the script window
65		-
66		-[[image:1657111556824-350.png]]
67		-
68		-
69		-[[image:1657111596157-325.png]]
70		-
71		-Click the Run button to execute the script
72		-
73		-
74		-)))
75		-1. (((
76		-For the Visual Studio development users they require to run the following inside a Visual Studio Command Shell as an administrator
77		-
78		-dotnet nuget add source https:~/~/pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json ~-~-name ebs-dev
79		-)))
80		-
81		-1.
82		-
83		-1.
84		-
85		-Also while we in the transition phase it might be helpful to add this link via this command:
86		-
87		->mklink /D c:\dev\src\Packages C:\dev\Packages
88		-
89		-
90		-[[image:1657115475686-934.png]]
91		-
92		-
93		-The URL's for different repositories to clone is as follows:
94		-
95		- ~-~-> Application Source Code
96		-
97		-[[image:1657115603808-846.png]]
98		-
99		-
100		-[[image:1657115842929-756.png]]
101		-
102		-For reference attached is the mappings of the new folders from old folders.
103		-
104		-
105		-If you want to start making changes follow the following process:
106		-
107		-
108		-1. (((
109		-Right click the migration folder and create a new branch via the TortoiseGit menu
110		-
111		-
112		-1. [[image:image-20220706143954-1.png]]
113		-)))
114		-1. specify branch name follow this pattern for now (names cannot have spaces use dashes -):
115		-
116		-1. feature/il-12345
117		-11. if it is issue log related you can add a -short-description if needed
118		-11. 12345 = replace with issue log number
119		-1. feature/12345
120		-11. if it is azure task related
121		-11. 12345 = replace with az workitem number
122		-1. feature/short-description
123		-11. if it has no work item associated to it
124		-
125		-1. make sure you select branch = master and switch to new branch is checked
126		-11. [[image:image-20220706143954-2.png]]
127		-
128		-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//.
129		-
130		-
131		-As always please reach out if you get stuck.
132		-
133		-
134		-Regards