![code on time view details code on time view details](https://blogs.sas.com/content/sasdummy/files/2017/07/splitview.png)
Open the shortcut menu for an item to see the contact options. To use the keyboard, hold down the Alt key and then press Left arrow or Right arrow to navigate the indicator options.įind linked bugs by selecting the bugs indicator or by pressing Alt+ 7.įind the author of an item by selecting the authors indicator or by pressing Alt+ 5.
#Code on time view details code#
IconĪ branch further away than a parent, child, or peerĪ merge from the parent branch to a child branchĪ merge from a child branch to the parent branchĪ merge from an unrelated branch (baseless merge)įind linked work items by selecting the work items indicator or by pressing Alt+ 8.įind linked code reviews by selecting the reviews indicator. The icon in the Branch column tells you how the branch is related to the branch you're working in. You can see when changes got merged, so you can determine which changes are included in your branch:įor example, your code in the Main branch now has the bug fix from the "Dev" branch:Ĭompare an incoming change with your local versionĬompare an incoming change with your local version by pressing Shift+ F10, or by double-clicking the changeset. You can review the change without leaving your current branch ("Main"): In the following screenshot, a bug fix was made in the "Dev" branch: Then, select the changes indicator or press Alt+ 6:įind incoming changes from other branches To find when your code was branched, navigate to your code in the child branch. You can find out how many people changed your code and how many changes were made in the main branch by pressing Alt+ 6: Your team may have multiple branches, for example a main branch and a child development branch, to reduce the risk of breaking stable code. This can help you find patterns in your team's changes and assess their impact. You can also see who changed your code over time. Some of these details appear in Team Explorer. 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.
![code on time view details code on time view details](https://c8.alamy.com/comp/2FNNY2A/programing-sql-php-source-code-on-screen-2FNNY2A.jpg)
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. 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).
#Code on time view details professional#
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.
![code on time view details code on time view details](https://www.computerhope.com/issues/pictures/chrome-view-page-source.jpg)
In the code map shortcut menu, select Show All References. To see relationships between the code and its references, create a code map.
![code on time view details code on time view details](https://static-aliyun-doc.oss-accelerate.aliyuncs.com/assets/img/en-US/6711417951/p6505.jpg)
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.