This project is read-only.

Question: When would I typically use shelving?

- J.D. Meier, Jason Taylor, Alex Mackman, Prashant Bansode


There are a number of common scenarios in which you would use shelving:
  • You are midway through making changes to a set of source code when new, higher-priority work is allocated (for example, an emergency bug fix is required). At this point you need to go back to a stable version of the code but do not want to lose your changes. You can shelve your code and easily retrieve it later.
  • You have not completed work at the end of the day but want to ensure that your current work is backed up on the server. By shelving your current changes, the changes are applied to the Team Foundation Server and can be retrieved by you (or others) on another day.
  • You want to discuss or review your partially completed code with a remote team member. Rather than e-mailing the code, you can shelve it and then have your remote colleague retrieve the files from the shelf.
  • You want to pass partially finished work to another developer for completion.

Additional Resources

Last edited Jul 19, 2007 at 12:15 AM by jtaylorsi, version 6


No comments yet.