Summary

• Page properties (3 modified, 0 added, 0 removed)
• Attachments (0 modified, 2 added, 0 removed)
  • image-20220706143954-1.png
  • image-20220706143954-2.png

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	+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	+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]]
	12	+)))
	13	+1. (((
	14	+run:
	15	+
	16	+
	17	+dotnet nuget add source https:~/~/pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json ~-~-name ebs-dev
	18	+)))
	19	+
	20	+1.
	21	+
	22	+1.
	23	+
	24	+Also while we in the transition phase it might be helpful to add this link via this command:
	25	+
	26	+>mklink /D c:\dev\src\Packages C:\dev\Packages
	27	+
	28	+
	29	+
	30	+For reference attached is the mappings of the new folders from old folders.
	31	+
	32	+
	33	+If you want to start making changes follow the following process:
	34	+
	35	+
	36	+1. (((
	37	+Right click the migration folder and create a new branch via the TortoiseGit menu
	38	+
	39	+
	40	+
	41	+1. [[image:image-20220706143954-1.png]]
	42	+)))
	43	+1. specify branch name follow this pattern for now (names cannot have spaces use dashes -):
	44	+
	45	+1. feature/il-12345
	46	+11. if it is issue log related you can add a -short-description if needed
	47	+11. 12345 = replace with issue log number
	48	+1. feature/12345
	49	+11. if it is azure task related
	50	+11. 12345 = replace with az workitem number
	51	+1. feature/short-description
	52	+11. if it has no work item associated to it
	53	+
	54	+1. make sure you select branch = master and switch to new branch is checked
	55	+11. [[image:image-20220706143954-2.png]]
	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	+Regards

image-20220706143954-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.rudim

Size

...	...	@@ -1,0 +1,1 @@
	1	+72.6 KB

Content

image-20220706143954-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.rudim

Size

...	...	@@ -1,0 +1,1 @@
	1	+30.3 KB

Content