Silas2
asked on
TFS newbie basic question
To use TFS in its most basic way as a developer, not admin, is this all I need to know:
Step #1 Start work: Get Latest Version
Step #2 No need to Check-Out , as check out auto when edit.
Local save as normal
Step #3 finish work, check in
would that be enough for me to join a team as a newbie, and be able to start work?
Step #1 Start work: Get Latest Version
Step #2 No need to Check-Out , as check out auto when edit.
Local save as normal
Step #3 finish work, check in
would that be enough for me to join a team as a newbie, and be able to start work?
ASKER
Do you use the work item stuff?
And all the exclude/include, I don't really have any idea what the real-life scenario where you would want that?
And all the exclude/include, I don't really have any idea what the real-life scenario where you would want that?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Oh I see, that makes sense. Thanks.
Shelving is useful for saving your changes without committing them to the branch.
For your #2, I wouldn't say that is always the case. Sometimes you may have files that aren't really editable, but for which you still need to check out and modify. As an example, one of my projects has a specification document checked into TFS. We publish this spec document along with the website. I have Microsoft Word on my machine, but I cannot guarantee that everyone does--since Word costs money. So whereas I edit my spec document in Word, when I publish the document I publish it as PDF, because Adobe Reader is free, and I can be reasonably assured that most anyone can read a PDF. So whenever I need to update the PDF, I still have to check it out in order to be able to save the updated Word document to the updated PDF>
If your team uses a build server, then you may want to gain a basic understanding of what it provides for you.