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

Some of the projects have been converted to start using our own nuget feed so to ensure you do not have any connectivity issues:

1. Make sure that you download and install the latest version of Git from https://gitforwindows.org/

1. make sure your VS is updated with the latest updates (critical)

2. install The Azure Artifacts Credential Provider and select the PowerShell helper script link

   

   Click the copy icons to copy the text

   

   Open Windows Powershell ISE as administrator and click the new button and paste the text in the script window

   

   

   Click the Run button to execute the script

    

3. For the Visual Studio development users they require to run the following inside a Visual Studio Command Shell as an administrator

   dotnet nuget add source https://pkgs.dev.azure.com/ebsphere/ebsphere/_packaging/ebs-dev/nuget/v3/index.json --name ebs-dev

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

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.

Regards