Changesets for TFS
Salesforce application development runs at the forefront of innovation and continuous improvement. Several changes happen in an endeavor to build a robust application. Salesforce development benefits from an effective change management framework to enable multiple developers to work concurrently and the ability to manage multiple versions of code to deploy them seamlessly across various Salesforce environments. Handling these changes efficiently improves the time-to-market of Salesforce applications. To accomplish that Salesforce development teams use various methods from Version Control Systems to spreadsheets and ZIP files. They are encouraged to integrate their code after working on a single task related to a module instead of integrating the changes from all the tasks of a module. As the latter method results in numerous code changes and if the code breaks it would be hard to figure out what specific changes caused it. Team Foundation Server, a leading Version Control System, offers a way to have traceability of the code changes without having to work in any specific manner.
Changesets for TFS
In TFS a changeset is created after every code check-in. This changeset consists of a set of files and their respective work items that could be user stories, product backlogs, bugs or issues. A Changeset number is created upon a successful commit, based on the number of files and the associated work items. This number can be used to trace back to the files related to a particular task and deploy its associated code changes to higher orgs easily.
AutoRABIT for TFS
AutoRABIT is an enterprise-scale Continuous Delivery suite for Salesforce. It is integrated with industry-leading Version Control Systems like GIT, SVN, TFS and Perforce to help enterprises deliver improved business performance by driving successful change and configuration management on the Salesforce platform.