TFS or Git
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Git Despite its higher learning curve I finally took the plunge recently myself. I can live without distributed blah blah blah blah whatever, and I don't care about hype one bit. But, what sold me was it's so much easier to branch and merge in git. Especially compared to SVN. TFS is pretty good about it, but still git shines there.
Jeremy Falcon
-
Git Despite its higher learning curve I finally took the plunge recently myself. I can live without distributed blah blah blah blah whatever, and I don't care about hype one bit. But, what sold me was it's so much easier to branch and merge in git. Especially compared to SVN. TFS is pretty good about it, but still git shines there.
Jeremy Falcon
I really only care about Source Control. Do you have any "getting started" resources?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
TFS at work. For personal projects, I have my own. :D
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
TFS and Git are not mutually exclusive? :confused: Do you mean TFVC, the Microsoft Team Foundation Version Control that not even Microsoft is using anymore? TFS supports both TFVC and Git, but I'd recommend Git. In fact, TFVC shouldn't even be an options anymore because, as said, not even its creator Microsoft uses it anymore. Branching and merging is a lot better and easier in Git. Besides, Git has become the industry standard making it easier to find help and documentation. I've also heard good things about Mercurial by the way. And I guess SVN is still an options too, although I never hear about it anymore. I'm not sure if those are supported in TFS though :)
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
I really only care about Source Control. Do you have any "getting started" resources?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Well, my intro resource was being a n00b to it and asking coworkers a ton of questions. So, I can't really recommend a good online resource. That being said, keep it simple to start with and work on a project with it. This link will get you going: git - the simple guide[^]. Also, if you're a PowerShell buff, installing A PowerShell environment for Git[^] will give you some fancy visual cues when you're in a project.
Jeremy Falcon
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
If you use VSO (Visual Studio online) it offers TFS and Git. At work we use Git through VSO.
Nish Nishant Consultant Software Architect Ganymede Software Solutions LLC www.ganymedesoftwaresolutions.com
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
TFS works well for me. However, the cool kids at work are clamoring for Git. I think they may know a thing or two more than me about Git, so I'm on a mission to educate myself on the subject before chiming in with my 2¢ worth. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Link I found interesting on git. GitFlow considered harmful | End of Line Blog[^] Don't think that explicitly mentions the following... A git repository only allows versioning for the repository. When you apply a version number or extract a version it applies do all files in the repository. This is fine for single projects. However consider what happens in an enterprise with an example setup. - Libraries (sub projects) A, B, C - Application X uses A and B - Application Y uses B and C In the above Git only allows for the following Scenario 1 - Repository: A - Repository: B - Repository: C - Repository: X - Repository: Y Scenario 2 - Repository: A, B, C, X, Y If you choose one then you must manage each of those. So a release of X means that three repositories must be 'manually' labeled. And each must be built. If you choose two then B has the same labels as A, and when you pull you get B even if you just want A. Mitigation strategies can be created but those still exist outside of Git itself. For example creating yet another repository to handle build tools (to insure labeling, dependencies, etc.)
-
Well, my intro resource was being a n00b to it and asking coworkers a ton of questions. So, I can't really recommend a good online resource. That being said, keep it simple to start with and work on a project with it. This link will get you going: git - the simple guide[^]. Also, if you're a PowerShell buff, installing A PowerShell environment for Git[^] will give you some fancy visual cues when you're in a project.
Jeremy Falcon
Are there any Agile tools that work (well) with Git?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I believe the standard is more or less GIT. We switch from Subversion to GIT (hosted on ButBucket) a year ago, and we use TortoiseGit as a front end. The transition was hard; learning curve is very steep. The thing with GIT is that it has a lot of advanced features that you need to keep clear of that most people do not use. Doing simple Code Versionning is easy. (clone, checkout, pull, push commit ...) Branching is fun and more or less seamless (we do branches for each issue) once you "get it". This is one tutorial that I used. [Git Tutorials and Training | Atlassian Git Tutorial](https://www.atlassian.com/git/tutorials)
I'd rather be phishing!
-
Are there any Agile tools that work (well) with Git?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I'm still new-ish to git myself, but there's always Jira[^] which will do that. It's like $10 if you host it yourself. As long the concepts are down I'd imagine you could find a way to adopt most tools to the workflow though. Anyway, here is the basic concept of agile within git: How Git fits into an agile workflow[^]. Since git makes branching much easier, you'll see people use them a lot more.
Jeremy Falcon
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I use Git begrudgingly. Worst part of the learning curve is that if you have a file X.txt in branch A but not in branch B when you switch branches from A to B X.txt vanishes. It will come back when you switch back as long as it was checked in. It focuses on the repository as a whole rather than individual files. Get a good ide for Git, they help and have all the features one normally needs. I'm enjoying GitKraken right now but have used SourceTree as well.
-
I use Git begrudgingly. Worst part of the learning curve is that if you have a file X.txt in branch A but not in branch B when you switch branches from A to B X.txt vanishes. It will come back when you switch back as long as it was checked in. It focuses on the repository as a whole rather than individual files. Get a good ide for Git, they help and have all the features one normally needs. I'm enjoying GitKraken right now but have used SourceTree as well.
MarkTJohnson wrote:
It focuses on the repository as a whole rather than individual files.
I find that's part of what makes branching incredibly easy in git though. Less is more.
Jeremy Falcon
-
A_Griffin wrote:
I am just so glad I work alone….
Hah! That makes two of us! I still have a coworker that does mostly non-coding stuff. I've made it almost 20 years without source control...code fearlessly! :laugh:
"Go forth into the source" - Neal Morse
-
MarkTJohnson wrote:
It focuses on the repository as a whole rather than individual files.
I find that's part of what makes branching incredibly easy in git though. Less is more.
Jeremy Falcon
To each his own. I prefer the old days with file locking. But the files disappearing between branches was is real PITA at times when you want to compare files.
-
To each his own. I prefer the old days with file locking. But the files disappearing between branches was is real PITA at times when you want to compare files.
MarkTJohnson wrote:
To each his own. I prefer the old days with file locking.
:-D Fair enough.
MarkTJohnson wrote:
But the files disappearing between branches was is real PITA at times when you want to compare files.
Well, you can do a diff across branches. Not sure what to click in Tortoise for it, but it has to support it since git does.
Jeremy Falcon
-
I'm using versioncontrol also for private stuff.
Wrong is evil and must be defeated. - Jeff Ello
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Git is an immense over kill. SO complex, so powerful, so much more than you need, but it works. Very very well. Take the time to get to know it, the online support is very good. You will, after a few years, wonder why you use anything else.
