Summary

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

Details

Page properties

Title

...	...	@@ -1,0 +1,1 @@
	1	+getting-started

Parent

...	...	@@ -1,0 +1,1 @@
	1	+Technical Documentation.Source Control.WebHome

Content

...	...	@@ -1,0 +1,65 @@
	1	+
	2	+
	3	+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**​.
	4	+
	5	+
	6	+Some of the projects have been converted to start using our own nuget feed so to ensure you do not have any connectivity issues:
	7	+
	8	+1. make sure your VS is updated with the latest updates (critical)
	9	+1. (((
	10	+install [[The Azure Artifacts Credential Provider>>url:https://github.com/Microsoft/artifacts-credprovider#setup]]
	11	+)))
	12	+1. (((
	13	+run:
	14	+
	15	+
	16	+dotnet nuget add source https:~/~/pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json ~-~-name ebs-dev
	17	+)))
	18	+
	19	+1.
	20	+
	21	+1.
	22	+
	23	+Also while we in the transition phase it might be helpful to add this link via this command:
	24	+
	25	+>mklink /D c:\dev\src\Packages C:\dev\Packages
	26	+
	27	+
	28	+
	29	+For reference attached is the mappings of the new folders from old folders.
	30	+
	31	+
	32	+If you want to start making changes follow the following process:
	33	+
	34	+
	35	+1. (((
	36	+Right click the migration folder and create a new branch via the TortoiseGit menu
	37	+
	38	+
	39	+
	40	+1. [[image:image-20220706143920-1.png]]
	41	+)))
	42	+1. specify branch name follow this pattern for now (names cannot have spaces use dashes -):
	43	+
	44	+1. feature/il-12345
	45	+11. if it is issue log related you can add a -short-description if needed
	46	+11. 12345 = replace with issue log number
	47	+1. feature/12345
	48	+11. if it is azure task related
	49	+11. 12345 = replace with az workitem number
	50	+1. feature/short-description
	51	+11. if it has no work item associated to it
	52	+
	53	+1. make sure you select branch = master and switch to new branch is checked
	54	+
	55	+11.
	56	+
	57	+
	58	+
	59	+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//.
	60	+
	61	+
	62	+As always please reach out if you get stuck.
	63	+
	64	+
	65	+