Versions Compared

Old Version 19

changes.mady.by.user John Sewchand (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Siamak Shirzad

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

(Please note If you have Chocolatey already installed, you can jump to step 4)

1. Open CMD Windows PowerShell as administrator 
2. run following in cmd shell to install Chocolatey package manager


Code Block
@"%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command "Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin"


3. run following in cmd shell to test Chocolatey installation

...

6. run following in cmd shell to verify git-tfs installation.

Code Block
git tfs help


Warning

If you don't have any installation from Visual Studio, you might get an error when running the above command

Image Added

I downloaded Team Explorer based on this website: https://devblogs.microsoft.com/devops/reintroducing-the-team-explorer-standalone-installer/ and I installed it.

Image Added 

After that, I choose the option "Not now, maybe later." and "Start Visual Studio"

Image Added Image Added

NOTE: You don't need to leave the visual studio open.

7. run following command if want to list all TFS branches that could be cloned (Please be careful to use this command as it might take long time.  Also be sure to replace appropriately with your TFS collection information)

...

Warning

If your codebase in TFS has sensitive information (eg. passwords), do not include them in your Azure Devops repository.  You can do one of two things:

  1. Remove them from the codebase, check the changed files back into TFS and then be sure to clone the latest code only (step #8).  You will lose all history in this case.
  2. If you clone all history (as in step #9), the passwords will still be available in the repo history.  Remove the culprit files from history as follows:
    1. In the cmd shell, navigate to your repo's folder (in the above example it was c:\tmp\migration\mpdis).
    2. (See this page for more detail regarding this step).   Run the following making sure to change the path-to-the-file to the actual path to the file (eg. src/web.config):  git filter-branch --force --index-filter "git rm --cached --ignore-unmatch path-to-the-file" --prune-empty --tag-name-filter cat -- --all
    3. You've now removed the culprit files from history.  You can re-create and add them to the repository later with sensitive information removed if you'd like.

NOTE: If there is a space in a folder name in path-to-the-file, place a slash"\" before the space. E.g. if the path is  My Project/Settings.settings, change it to My\ Project/Settings.settings. Otherwise, the above command does not remove specified file.

10. Check Now navigate to the location where you cloned your repository (eg. c:\tmp\migration\mpdis).  Then you can check history:

Code Block
git log

...