I have explained few of the enhancements available in TFS Web Portal for Version Control in Part 1. There are lot more really useful enhancements available.
1. It is possible to view a file as of in a given changeset and download the changeset version of the file to local machine.
2. Explore as a changeset version allows to view entire solution as of that particular version.
As of changeset version can be explored.
3. Download a solution as of a changeset version.
4. Annotate a chageset version of a file.
5. Compare a file for given two changesets.
6. Shelveset exploring has similar capabilities to changesets except few like explore as of version which is obvious since it is not committed, so no version is available.
View shelveset content, add comments/discussions, download shelveset file(s), compare with changesets are few of the available features.
7. Sharing a changeset as an email, enhances team collaboration.
Can share with multiple team members and add more custom content to email is possible.
Discussions etc. of the changeset are shrared via email and links are added for easy access.
8. Similar to changeset a shelveset can also be shared via email.
9. Rename history of the files can be viewed and show hide options available.
10. Branched history of file can be viewed with show hide options.
Let’s have look in to more new useful features of TFS2013.4 in coming posts.
Subscribe to:
Post Comments (Atom)
Popular Posts
-
Dynamic block allows to create nested multi level block structures in terraform code. Conditional usage of such blocks are really useful in...
-
In Azure DevOps YAML pipelines there are several functions available for you to use. replace is such a useful function, which you can use t...
-
We have discueed, that we have to use an environment variable to handle input parameter default values, if we are using trigger for workflo...
-
Adding Azure Container Registry (ACR) service connection to Azure DevOps is really simple as described in " Create Service Connection ...
-
Some times a silly mistake can waste lot of time of a developer. The exception “System.IO.IOException: The response ended prematurely.” whil...
No comments:
Post a Comment