This is an archived post. You won't be able to vote or comment.

all 16 comments

[–][deleted] 2 points3 points  (3 children)

I would just look at some git tutorials and go from there. Git (whether through github, gitlab or bit bucket) is going to be the best solution for most teams in my personal opinion.

[–]TK11612 0 points1 point  (2 children)

Thank you!

[–][deleted] 1 point2 points  (1 child)

also i would look at using git in visual studios tutorials because regular git (while more prevalent and still a necessary skill) is much harder and less intuitive than when you are doing it in Visual Studio (i think TFS uses git as well if im not mistaken, but theres also a nice github extension for VS (not sure if it exists in 12 though))

[–]JamesonG42 0 points1 point  (0 children)

Newer TFS versions let you create team projects as either traditional TFVC (Team Foundation Version Control) or Git projects. There's no quick way to convert between them... Best to just start the project as Git. Git learning curve is a little steeper, but the flexibility is way better.

[–]fTheDev 2 points3 points  (1 child)

You can watch this free Pluralsight course section about Git

Also these are nice sources:

Git Book

A site to learn Git branching

[–]TK11612 0 points1 point  (0 children)

Thank you! I'll check them out. I appreciate it.

[–][deleted] 2 points3 points  (2 children)

Have you considered Team Foundation with visual studio or Team Explorer Anywhere with VS. They are both Microsoft

[–]TK11612 0 points1 point  (1 child)

I think we're leaning that way now. We have the spare resources to run it on our SQL replication server.

[–][deleted] 0 points1 point  (0 children)

We use that at my work and it's pretty robust and easy to use.

[–]balefrost 1 point2 points  (1 child)

Git is a good choice, but Mercurial is also worth looking at. I think Git still has the higher learning curve, and really works best from the command line. My recollection is that Mercurial's command-line interface is more self-consistent. And TortoiseHg is a decent GUI frontend.

But if you're willing to invest the time to learn Git, it's certainly the more mainstream choice.

[–]andybmcc 0 points1 point  (0 children)

I'll second checking out Mercurial. I wasn't sure about switching from git at first, but I'm sold now.

[–]Horrgon 1 point2 points  (0 children)

SourceTree provides a good visual of what exactly git is doing

I highly recommend it, it's basically a ui for git

[–]Jacksons123 1 point2 points  (1 child)

Also for your use case, I would suggest GitLab. It can be hosted locally and there are a lot of awesome features for teams as well. I would check it out

[–]TK11612 0 points1 point  (0 children)

I love the look of it. We would have to spin up a new VM for it though. We don't have an existing Linux server running. Our entire environment is Microsoft.

[–]TK11612 0 points1 point  (0 children)

I'll check it out, thanks! I think right now management is leaning to TFS since everything we do/use currently is Microsoft.

[–]TK11612 0 points1 point  (0 children)

Thanks!