locked
difference between get lates and specific RRS feed

  • Question

  • why get latest misses updating some files while get specific works
    Mark Answered, if it solves your question
    Rohit Arora
    Thursday, July 21, 2011 2:32 PM

Answers

  • I do not think that you are describing standard behavior.

    Get latest gets the actual file in case the local file is outdated as compared with the server version; TFS does not check the actual file contents; when you perform get latest, db is updated with your workspace version so on next get latest your actual hard drive is not examined even.

    So basically if there is new version at source control, get latest should bring it to you. The issue I was seeing a lot is people modifying local version locally (without performing check in), and then on get TFS naturally does not update version (as local file is not checked for changes). Then you indeed may resort to get specific to get that file (with "Force" checkbox checked).

    Overall, in shared environment the users should be able to perfom get latest as needed; the whole architecture of TFS is designed to make get latest operation really fast.

    Hopefully, you can start to see some implications of the way in which TFS workspaces are used by the server. For example, if you un-mark a file as read/write, edit it and then do a "Get Latest" on that file then it will not be replaced with the latest version from the server (because you never told the server (by checking out the file) you were messing with that file so it assumes it you didn't). In that scenario you would want to use the "Get Specific..." option to force a get of the file. Read more on this blog post http://www.woodwardweb.com/teamprise/000333.html.  

    Thus I'd say the issues you are seeing are related more to operation procedure than to the tool.

    HTH
    Cheers, Tarun


    Please remember to mark the replies as answers if they help.

    Tarun Arora

    Blog: http://geekswithblogs.net/TarunArora  Subscribe in a reader

    Thursday, July 21, 2011 6:27 PM

All replies

  • I do not think that you are describing standard behavior.

    Get latest gets the actual file in case the local file is outdated as compared with the server version; TFS does not check the actual file contents; when you perform get latest, db is updated with your workspace version so on next get latest your actual hard drive is not examined even.

    So basically if there is new version at source control, get latest should bring it to you. The issue I was seeing a lot is people modifying local version locally (without performing check in), and then on get TFS naturally does not update version (as local file is not checked for changes). Then you indeed may resort to get specific to get that file (with "Force" checkbox checked).

    Overall, in shared environment the users should be able to perfom get latest as needed; the whole architecture of TFS is designed to make get latest operation really fast.

    Hopefully, you can start to see some implications of the way in which TFS workspaces are used by the server. For example, if you un-mark a file as read/write, edit it and then do a "Get Latest" on that file then it will not be replaced with the latest version from the server (because you never told the server (by checking out the file) you were messing with that file so it assumes it you didn't). In that scenario you would want to use the "Get Specific..." option to force a get of the file. Read more on this blog post http://www.woodwardweb.com/teamprise/000333.html.  

    Thus I'd say the issues you are seeing are related more to operation procedure than to the tool.

    HTH
    Cheers, Tarun


    Please remember to mark the replies as answers if they help.

    Tarun Arora

    Blog: http://geekswithblogs.net/TarunArora  Subscribe in a reader

    Thursday, July 21, 2011 6:27 PM
  • +1 Good description Tarun :-)
    We are volunteers, if the reply help you mark it as your answer. thanks!!
    My Blog
    Saturday, July 23, 2011 9:38 PM