index > Team Foundation Server - Version Control > VS SP1

VS SP1

Does anybody know if there is going to be an SP1 for TFS after the VS SP1 comes out? TFS Source Control is killing us with all of it's buggy-ness. I swear TFS is such productivity suck,but it seems like it's got potential. We're hoping MS will fix some of this nonsense with a SP, but if it's not coming we'd like to cut our losses and move to SVN.
Any service pack info from you MS insiders?

TheGeoff

Hello,

yes, there will be SP1 for TFS - please look at Brian's post

Regards

Michal Malecki

I checked out his post. It'd be really nice if they had a list of issues they're planning to fix or when the SP will drop. The whole TFS thing is really flaky and consumes way too much of our time due to its various fits. The one that plagues us the most is the fact that sometimes it'll neglect to check in a few files from a group check-in. That has cost us a lot of time and frankly it made us loose confidence in TFS.
Also, I'm really curious to see if they will remain stubborn about fixing the "Get Latest Before Checkout" bug. Yep, I called it a bug. I read the explanation and I don't care what they say. It was a dumb decision on their part not to have the option and until they own up to it I don't hold out much hope for the product.

Hopefully, SP1 will make TFS behave in a tolerable fashion. It's a hard sell to get the company to walk away from a product that they spent so much money on. Not to mention it??l be a royal pain to move Source Control providers in the middle of our project.

-Geoff

TheGeoff

Hello,

could you describe what you mean by "neglect to check in a few files from a group check-in", maybe we can help you.

Michal Malecki

Sure. Anything would help.
Usually it happens when checking in large groups of files in multiple projects. One or two files won't get checked in. We don't lose the changes, the files remain checked out on the client and the updates don't make it to the server. The good news is no changes are permently lost, the bad news is whenever this happends builds break, phantom bugs are introduced, due to the couple of old files.
I was chalking it up to user error, but it's happened to most of us on the team and continues to happen. We've tried to use the Source Control Explorer exclusively for check-ins instead of the Solution Explorer since the Solution Explorer tends to loose the plot pretty easily when it comes to Source Control. It happens less now, but still occurs. We have to double check all check-ins to mitigate the problem, but that's not much of a solution.
We're using VS 2005 Team System.

Thanks,
Geoff

TheGeoff

It's easy to miss something when there is a large # of changes. Luckily, shelvesets make verifiable buddy builds easy. Instead of using the Checkin button on the Pending Changes toolwindow, click Shelve, and uncheck "preserve changes locally." Then have someone else unshelve in their workspace and test. If all is well, the original user unshelves back into their workspace and safely checks in.

Richard Berg MSFT

Are you saying you are not getting atomic check-ins? That some of the files check-in but not all the files check-in?

Principal Consultant, Magenic -- http://blogs.manicprogrammer.com/michaelruminer

Michael Ruminer

Also curious... in regards to the 'get latest on checkout' if you were working on code from a shelveset and needed to check out a file for edit would you always want the version on the server?

I'm curious how people see shelvesets working for them when they flip the flag for 'get latest on checkout' which invariably is going to be provided at some point (look at the latest MSSCCI Provider- it already has it) and they are working on code from a shelveset- will it cause problems or is the developer with that flag flipped willing to take on the task of integrating those changes from the latest version of some to many files into the changeset.

Principal Consultant, Magenic -- http://blogs.manicprogrammer.com/michaelruminer

Michael Ruminer

reply 8