|
My favourite "feature" is that deleting a file from the Solution Explorer then performing a checkin doesn't actually commit the delete; you have to open Team Explorer then check in there for the deletes to actually commit...crazy.
This also causes complete havok with NuGet which attempts to delete a package that doesn't get deleted so it can't be replaced. I find I have to checkout the whole kit and kaboodle, manually delete the packages, check everything back in, in Team Explorer so packages actually get deleted, then checkout once more, then add the new packages then perform another check in.
|
|
|
|
|
...and if you rename or move that file before deleting it the check in comes to a screeching halt because *gasp* the file isn't there anymore. TFS gets itself into more existential conundrums than a nihilist week-long retreat.
I know MS. Clearly I'm not "holding it the right way".
|
|
|
|
|
I completely agree. Whoever designed the UI for TFS online is a total moron. Completely confusing.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Kevin Marois wrote: the UI for TFS online The forms can be customized, by the way.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Straight outta the box it's a total mess. It's not at all intuitive. There's no clear indication where you are or how to do even the simplest things.
Every try deleting a project??? That took a bit of Googling to finally find the right page and then the right little drop down widget thingy.
Add a project.... and wait 10 minutes while it's created.. WTF could possibly take so long to create a few records in a DB somewhere?
Wanna give someone rights? LOL - Good luck trying that.
Then, after alllll that - you think I'm gonna "customize" it... hell I can't figure it out in its default configuration. Screw customizing.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Git, of course.
Or, Mercurial (Hg)
Visual SourceSafe should'a been your warning for TFS.
|
|
|
|
|
raddevus wrote: Git, of course
Sadly I'm forced to use the source control system that the company is using.
Marc
|
|
|
|
|
I used to wrap my directories in a git repository, but when I tried that here, Visual Studio saw that I had a git repository and would no longer show me the normal tfs team stuff and would only offer its git interface in the team tab...even Visual Studio knows that git is superior to tfs.
|
|
|
|
|
Have been using it quite happily for a number of years. Not the best nor the worst tool. However, I have persuaded management in a few places that it would be best if we employed a TFS consultant to set it up initially to suit our needs and then we could move on from there. That works well. Also depends on how complex you want/need to make the branching model and what other parts of it you need to use.
|
|
|
|
|
I don't like it either, but I have to use it at work. No performance issues though, and branching and merging is easy through VS.
|
|
|
|
|
We use it via the VS IDE as much as possible.
Online: what a debacle. Truly mind boggling.
cheers
Chris Maunder
|
|
|
|
|
Well i wanted to use TFS but then i saw TeamCity and fell in love
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
|
S.L.O.O.O.W!
I gave up on it after three or four weeks.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Using Visual Studio Team Services here and it's great, naturally not using TFVC for source control but as VSTS supports Git why would you?
Back in the days of TFS 2010 then yeah, that sucked pretty badly. 2013 got much better but Team Services is where it's at for me.
Eagles may soar, but weasels don't get sucked into jet engines
|
|
|
|
|
I setup TFS 2013-15 in our company, a complete switchover from our previous source control and bug tracking.
We use local TFS, not TFS online. For source control everything is instantanous, and we're using TFVC not Git (which has a local repo). I think it's fantastic and the whole company loves it.
Keep in mind we're all using Visual Studio 2015 so the integration is basically flawless.
|
|
|
|
|
same here TFS works great for us (using SCRUM) - also wrote some custom server-plugins and Tools - you can do a lot with the API - I like the "open" way of MS.
But I can understand the critics about TeamExplorer UI in VS...
|
|
|
|
|
We use our own networked instance and its been fine.
The only place I find it lacking is I'd like to be able to find in files without having to get latest.
|
|
|
|
|
My previous employers used TFS Online.
We could never find anything.
I agree it's a mess, never got used to it.
Now using JIRA.
It took a little getting used to, but at least I can find stuff there now.
|
|
|
|
|
TFS uses wrong terminology, as a result it always does something completely unexpected.
If you have to use it (company decision) then employees must be properly trained at first place.
If the company doesn't do the training prerequisite than the use of TFS is clunky and TFS functionality is limited.
Finaly conclusion: run away of it unless your company is (big) Microsoft Partner (or something).
|
|
|
|
|
Terminology is pretty simple:
Check-out to start working on a file;
check-in to send files that are checked out into the main repository;
Rollback to undo a check-in;
Undo to undo a check-out (revert changes).
You have a command line, an integration with the file system or the visual studio integration (the best option, where things are pretty clear).
It is much simpler than any other system, it's user interface in Visual Studio is very simple and straightforward - I teach it to newbies in 5 minutes.
|
|
|
|
|
I use Subversion and have been using it for years with no problems.
I agree with everyone else here. TFS is not very intuitive at all and no matter how long I used it I still couldn't remember that there were two separate interfaces to do various tasks.
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
I've been using it for the last two years and for the most part find it no worse or particularly better than the others. What I don't like is Microsoft changing the interface and there is no notice until after the fact when they get around to sending an email. What makes this worse is they don't keep the documentation current so you try to find out how to do something and the doc doesn't match.
|
|
|
|
|
I kinda think the answer is, "poorly".
We changed from TFS to git earlier this year. Sure, it takes a while to get used to the local and remote repos in git, but once you're past that, you no longer have the frustrating little "nuances" of TFS mentioned in many of the other replies.
|
|
|
|
|
Have used it for years. Works fine.
|
|
|
|