You can also see who changed your code over time. In Visual Studio 2019 version 16.8 and later, these details will appear in Git Changes. Some of these details appear in Team Explorer in Visual Studio 2019 version 16.7 and earlier.
Depending on whether you are using TFVC or Git, there are options to compare the versions of the file, view details and track the changeset, get the selected version of the file, and email the author of that change. To get more details about a change, right-click that item. When your files are in a Git repository and you choose the code element-level changes indicator, this is what you see:įind changes for an entire file in the file-level indicators at the bottom of the window:įile-level indicators are not available for C# and Visual Basic files. To see a detailed history of all the changes, including those from more than a year ago, choose Show all file changes: If your code is stored in Team Foundation Server, you can change the time period by running the TFSConfig command with the CodeIndex command and the /indexHistoryPeriod flag. The default time period is the last 12 months. This is what you see when you use Team Foundation Version Control (TFVC) in Team Foundation Server or Azure DevOps Services: Code element-level indicators are available for C# and Visual Basic code. vb, you get CodeLens details for the entire file in one place at the bottom of the window ( file-level indicators).Ĭode element-level indicators let you see who changed your code and what changes they made.
If your Git repository is hosted in TfGit, you also get links to TFS work items.įor file types other than. Microsoft Teams or Skype for Business to contact your team from the code editorįor C# or Visual Basic code that's stored with Team Foundation Version Control (TFVC) or Git, you get CodeLens details at the class and method levels ( code element-level indicators). Visual Studio Enterprise or Professional editionĪzure DevOps Services, Team Foundation Server 2013 or later, or Git Or, review changes before they're merged into your code so you can better understand how changes in other branches might affect your code.
Inspect your code's history to find out what happened to your code. In the code map shortcut menu, select Show All References. To see relationships between the code and its references, create a code map. To open the file that contains the reference, double-click the reference. To view the referencing code, mouse over the reference in the list. However, there may be references in other items such as. If the indicator shows 0 references, you have no references from C# or Visual Basic code.
0 kommentar(er)
