Hi Team

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​.

Prerequisites

1. Install WinMerge
   1. winget install -e --id WinMerge.WinMerge
2. Install Notepad++
   1. winget install -e --id Notepad++.Notepad++
3. Install VisualStudio 2022
   1. winget install -e --id Microsoft.VisualStudio.2022.Professional
4. Install VisualStudio Code
   1. winget install -e --id Microsoft.VisualStudioCode
5. Install Wix Toolset
   1. winget install -e --id=WiXToolset.WiXToolset

Extensions

1. Wix v3 - Visual Studio 2022 Extension
2. Microsoft Visual Studio Installer Projects 2022
3. Web Compiler 2022+

Source control installation

1. Install Git for Windows
   1. winget install -e --id "Git.Git"
2. Install tortoisegit
   1. winget install -e --id TortoiseGit.TortoiseGit
3. Setup the nuget feed

Also while we in the transition phase it might be helpful to add this link via this command:

mklink /D c:\dev\src\Packages C:\dev\Packages

clone to here: C:\dev\ebsphere\migration\

The URL's for different repositories to clone is as follows:

 --> Application Source Code

For reference attached is the mappings of the new folders from old folders.

If you want to start making changes follow the following process:

1. Right click the migration folder and create a new branch via the TortoiseGit menu

   1. 
2. specify branch name follow this pattern for now (names cannot have spaces use dashes -):

1. feature/il-12345
   1. if it is issue log related you can add a -short-description if needed
   2. 12345 = replace with issue log number
2. feature/12345
   1. if it is azure task related
   2. 12345 = replace with az workitem number
3. feature/short-description
   1. if it has no work item associated to it
       
4. make sure you select branch = master and switch to new branch is checked
   1. 

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.

As always please reach out if you get stuck.