Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In Subversion there is a pattern called Vendor branches to keep track of changes made by my self in a third party project. I´am not really sure how to do this in TFS, are there any best practicies? Is this procedure called anything else in TFS? I cant find anything like this behaviour.
In svn, vendor branches are just a convention, like the trunk/tags/branches top folders are just convention. You can implement the same convention in TFS.
If you are a third party contributor to a project, and have TFS access, your own branch does make sense. One advantage of this pattern is that the owner of this project can give you control over your vendor folder, and you can have your own set of sub branches, which you can merge into each other, or the project owner can merge into his trunk or version branches.