Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-nuget-feed
	1	+getting-started

Parent

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

Content

...	...	@@ -1,6 +1,28 @@
1		-1. Make sure your VS is updated with the latest updates (critical)
	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	+**Prerequisites**
	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]]
	12	+
	13	+**Source control installation**
	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. Install
	18	+
	19	+
	20	+
	21	+
	22	+
	23	+1. make sure your VS is updated with the latest updates (critical)
2	2	1. (((
3		-Install [[The Azure Artifacts Credential Provider>>url:https://github.com/Microsoft/artifacts-credprovider#setup]] and select the **PowerShell helper script **link
	25	+install [[The Azure Artifacts Credential Provider>>url:https://github.com/Microsoft/artifacts-credprovider#setup]] and select the **PowerShell helper script **link
4	4
5	5	[[image:1657111373296-938.png]]
6	6
...	...	@@ -16,10 +16,67 @@
16	16
17	17	[[image:1657111596157-325.png]]
18	18
19		-Click the Run button to execute the script.
	41	+Click the Run button to execute the script
	42	+
	43	+
20	20	)))
21	21	1. (((
22		-For the Visual Studio development user they need to run the following inside a Visual Studio Command Shell as an administrator.
	46	+For the Visual Studio development users they require to run the following inside a Visual Studio Command Shell as an administrator
23	23
24	24	dotnet nuget add source https:~/~/pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json ~-~-name ebs-dev
25	25	)))
	50	+
	51	+1.
	52	+
	53	+1.
	54	+
	55	+Also while we in the transition phase it might be helpful to add this link via this command:
	56	+
	57	+>mklink /D c:\dev\src\Packages C:\dev\Packages
	58	+
	59	+
	60	+[[image:1657115475686-934.png]]
	61	+
	62	+
	63	+The URL's for different repositories to clone is as follows:
	64	+
	65	+ ~-~-> Application Source Code
	66	+
	67	+[[image:1657115603808-846.png]]
	68	+
	69	+
	70	+[[image:1657115842929-756.png]]
	71	+
	72	+For reference attached is the mappings of the new folders from old folders.
	73	+
	74	+
	75	+If you want to start making changes follow the following process:
	76	+
	77	+
	78	+1. (((
	79	+Right click the migration folder and create a new branch via the TortoiseGit menu
	80	+
	81	+
	82	+1. [[image:image-20220706143954-1.png]]
	83	+)))
	84	+1. specify branch name follow this pattern for now (names cannot have spaces use dashes -):
	85	+
	86	+1. feature/il-12345
	87	+11. if it is issue log related you can add a -short-description if needed
	88	+11. 12345 = replace with issue log number
	89	+1. feature/12345
	90	+11. if it is azure task related
	91	+11. 12345 = replace with az workitem number
	92	+1. feature/short-description
	93	+11. if it has no work item associated to it
	94	+
	95	+1. make sure you select branch = master and switch to new branch is checked
	96	+11. [[image:image-20220706143954-2.png]]
	97	+
	98	+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//.
	99	+
	100	+
	101	+As always please reach out if you get stuck.
	102	+
	103	+
	104	+Regards