Is there a white paper explaining why Team Foundation Version Control sucks ?
-
I've gotten used to git (Mostly thanks to the GitKraken product), but I do long for the days of locking a file so no one else could modify while I was.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
Dear dog, I thought GIT sucked... but the winner goes to TFVC It seems in all my years of development, I've moved forward with Version Control. RCS -> CVS -> Subversion -> git but going from git to TFVC feels like a step back. Maybe there's just something I don't get from the system.
CI/CD = Continuous Impediment/Continuous Despair
Git sucks. TFS is awesome.
-
It seems MS itself is abandoning TFVC (or whatever name they give it this week) in favor of git, internally, or at least that's the impression I got back when I was working for someone who had a contract with them. Is someone actually moving from git to TFVC, or have you changed companies, and the new one simply has never used git before and you're comparing your experiences?
New company. I know they already have some products on git. Moving to git is in the plan.
CI/CD = Continuous Impediment/Continuous Despair
-
New company. I know they already have some products on git. Moving to git is in the plan.
CI/CD = Continuous Impediment/Continuous Despair
Gotcha. Since git is gaining so much in popularity, I just had to ask. Seems like everyone's moving in that direction, and not the opposite way. Personally, I just use TFS through Visual Studio and I'm absolutely fine with it. Git, despite the support built into VS for it, seems to really encourage people to work at a command prompt. And frankly, when things go wrong, I'd rather figure out menu options than command line switches.
-
Dear dog, I thought GIT sucked... but the winner goes to TFVC It seems in all my years of development, I've moved forward with Version Control. RCS -> CVS -> Subversion -> git but going from git to TFVC feels like a step back. Maybe there's just something I don't get from the system.
CI/CD = Continuous Impediment/Continuous Despair
Maximilien wrote:
Maybe there's just something I don't get from the system.
It's not you.
Latest Articles:
A Lightweight Thread Safe In-Memory Keyed Generic Cache Collection Service A Dynamic Where Implementation for Entity Framework -
Git sucks. TFS is awesome.
Strongly agree. :thumbsup: /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Gotcha. Since git is gaining so much in popularity, I just had to ask. Seems like everyone's moving in that direction, and not the opposite way. Personally, I just use TFS through Visual Studio and I'm absolutely fine with it. Git, despite the support built into VS for it, seems to really encourage people to work at a command prompt. And frankly, when things go wrong, I'd rather figure out menu options than command line switches.
At work we moved from TFVC to Git in 2018. But all my personal code is hosted in TFVC. I personally prefer its ease of use. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
At work we moved from TFVC to Git in 2018. But all my personal code is hosted in TFVC. I personally prefer its ease of use. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
I've gotten used to git (Mostly thanks to the GitKraken product), but I do long for the days of locking a file so no one else could modify while I was.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
MarkTJohnson wrote:
I do long for the days of locking a file so no one else could modify while I was
That 100% does not scale. If you're a team of two... fine. If you're an enterprise that flat-out fails on so many levels. You can't block one person from doing work while you lock a file. It's better to just learn how to merge.
Jeremy Falcon
-
Git sucks. TFS is awesome.
Git is awesome. I know for a fact the only peeps that hate it are the peeps that don't know it. Name one thing TFS does better... I'm waiting.
Jeremy Falcon
-
Dear dog, I thought GIT sucked... but the winner goes to TFVC It seems in all my years of development, I've moved forward with Version Control. RCS -> CVS -> Subversion -> git but going from git to TFVC feels like a step back. Maybe there's just something I don't get from the system.
CI/CD = Continuous Impediment/Continuous Despair
Stick with git. It'll take you much further and make you more flexible.
Jeremy Falcon
-
MarkTJohnson wrote:
I do long for the days of locking a file so no one else could modify while I was
That 100% does not scale. If you're a team of two... fine. If you're an enterprise that flat-out fails on so many levels. You can't block one person from doing work while you lock a file. It's better to just learn how to merge.
Jeremy Falcon
I know how to merge, I just wish I understood why some things throw merge conflict when there is no conflict, you are just changing a particular line. >>>>> New Code This line says B ===== This line says A <<<<< Old Code Why is that a merge conflict?
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
Gotcha. Since git is gaining so much in popularity, I just had to ask. Seems like everyone's moving in that direction, and not the opposite way. Personally, I just use TFS through Visual Studio and I'm absolutely fine with it. Git, despite the support built into VS for it, seems to really encourage people to work at a command prompt. And frankly, when things go wrong, I'd rather figure out menu options than command line switches.
Get yourself a Git GUI, SourceTree, GitKraken, etc. Here's a list 10 Best Git GUI Clients for Windows in 2023[^]
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
Get yourself a Git GUI, SourceTree, GitKraken, etc. Here's a list 10 Best Git GUI Clients for Windows in 2023[^]
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
"10 Best Git GUI Clients"? :wtf: 10? That's...not good. IMO. I use Visual Studio. I don't want to launch a separate tool just for source control. A Git client ought to be integrated with the tool that lets you write that source. If MS can't do a decent job (and that seems to be the case), then it's got an extension architecture.
-
Dear dog, I thought GIT sucked... but the winner goes to TFVC It seems in all my years of development, I've moved forward with Version Control. RCS -> CVS -> Subversion -> git but going from git to TFVC feels like a step back. Maybe there's just something I don't get from the system.
CI/CD = Continuous Impediment/Continuous Despair
I haven't run into any issues with using Git. I use Git via Visual Studio and Azure DevOps Repos, and to me, it is seamless. I get the idea of a local repo and a remote repo, with branching, that Git uses. I have used Bitbucket and Subversion, liked both, and found I like Git more, especially for team use.
-
Gotcha. Since git is gaining so much in popularity, I just had to ask. Seems like everyone's moving in that direction, and not the opposite way. Personally, I just use TFS through Visual Studio and I'm absolutely fine with it. Git, despite the support built into VS for it, seems to really encourage people to work at a command prompt. And frankly, when things go wrong, I'd rather figure out menu options than command line switches.
I've been using Git in VS for several years, and never had to use a command prompt for anything. The UI always provided everything I needed.
-
I know how to merge, I just wish I understood why some things throw merge conflict when there is no conflict, you are just changing a particular line. >>>>> New Code This line says B ===== This line says A <<<<< Old Code Why is that a merge conflict?
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
Depends on the line and the direction of the merge. Something like that isn't always a merge conflict. Sometimes it is... usually more so on a rebase than a merge in my experience. I've even seen whitespace trip git up. So, it's not perfect in the fact it will always be automatic. That being said, even if git were bad at merges (it's not... it's better than most)... handling a conflict here and there is still better than preventing people from working.
Jeremy Falcon
-
I've been using Git in VS for several years, and never had to use a command prompt for anything. The UI always provided everything I needed.
More power to you. Everybody should be blessed with that sort of experience. Maybe what we did deviated from what was made available through the GUI, but we were strongly encouraged (by those who were familiar with the system) to "just do everything from the command line".
-
Git is awesome. I know for a fact the only peeps that hate it are the peeps that don't know it. Name one thing TFS does better... I'm waiting.
Jeremy Falcon
I fully agree. Based purely on my experience, I'll readily admit I'm not a fan of Git, but fully acknowledge that this is entirely because I don't know it well enough. I have zero doubt, at this stage, Git is the superior product. I worked with a guy who *loved* it, and his enthusiasm for it was contagious. Who gets excited about TFS?? :-)
-
More power to you. Everybody should be blessed with that sort of experience. Maybe what we did deviated from what was made available through the GUI, but we were strongly encouraged (by those who were familiar with the system) to "just do everything from the command line".
That is not unusual. There are a lot of people whose experience came up through non-Windows OSs that had nothing but a command line in most cases. They tend to want to force that 1990s way of interface on others now. My point is that using Git in Visual Studio has been around with a GUI interface for years. If the less informed (like those telling you to use command line) choose not to use it, that is their problem, and it sounds like they made it your problem with which to deal. Sorry they hold you back like that.