I think I agree with Howard that the emphasis on reporting can encourage process > people treatment. I've seen that in 2 out of the 3 companies where I've used TFS.
My big problem with TFS is that I can't run our build scripts locally. So rather than follow good CI practices where everyone ones build and deployment, it falls into the terroritory of a few people. And I'd rather be using psake to structure the build... Here are two specific problems with TFS/MSVS integration: 1) When you edit it file for the first time, it will automatically checkout just that file. This is bad as now you have the latest for some files but not others- and the result may not even compile. 2) As you may have seen, Visual Studio doesn't save .CSPROJ or SLN changes immediately, only after you exit or "save all". If you try to get latest while such changes are unsaved, and their are changes to merge for a CSPROJ or SLN file, well you can' t merge you're unsaved changes. VS gets confused, you either lose the merge credit or lose your unsaved changes. On Wed, Jan 26, 2011 at 9:44 AM, Scott Koon <[email protected]> wrote: > > In my experience the main pain points surrounding TFS have been: > 1) Weird file locking, sometimes TFS will tell me that I have the file > locked when I don't. > 2) Branching seems to be a heavyweight operation and that makes people > hesitant to branch. > 3) GUI is slow and the CLI tools still pop up GUI windows(?!) > 4) The workflow is integrated. This might sound like a good thing, but in > reality it means that people try to incorporate the default workflow into > their business process and it never quite meets everyones needs. You can try > to find different scrum/agile templates out there but they are kind of a > pain to install and modify and again, don't quite meet your needs > 5) People don't use shelves frequently enough. > > -- > You received this message because you are subscribed to the Google Groups > "Seattle area Alt.Net" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/altnetseattle?hl=en. > -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
