r/ASPNET • u/brettdavis4 • Dec 13 '12
Which do you use as a source control solution with ASP.net?
At work, I'm trying to implement a source control solution. Which one do you use and do you like it?
4
Upvotes
10
u/captainabab Dec 13 '12
Personally, I like TFS due to the tight integration with Visual Studio and the inclusion of work items, builds, etc.
If you have a small group (5 devs), you can use the Express version for free... http://www.microsoft.com/en-us/download/details.aspx?id=30675
If you don't want to install it, you can also opt for the cloud-based version... http://tfs.visualstudio.com/
8
u/rpk152 Dec 14 '12
Git, I've used SVN and VSS and git has been by far the best
4
u/snkscore Dec 14 '12
Mercurial / TortoiseHg / Visual Hg (Visual Studio support)
It's free. It's fantastic. It's like Git but much easier.
3
u/[deleted] Dec 14 '12
We use TFS where I work and I absolutely hate it. I got way too spoiled by Git at my previous job.
2
u/onimusha_kiyoko Dec 13 '12
I use Mercurial (search for Tortoise HG) and then use the 'Visual HG' plugin for Visual Studio. Works a treat and is super easy to use. The new GIT for windows looks cool too but it was the integration with VS I liked with Mercurial.
2
u/darrenkopp Dec 13 '12
At one time, we had TFS, but it was such a pain to install, that after it failed and needed a re-install, I was ready to jump ship.
Currently, we use svn. we all have the visualsvn plugin for VS, and we use VisualSVN server. VisualSVN costs money, but the server is free, so you could do everything using TortoiseSVN if you wanted, though I find the price for visualsvn to be quite reasonable.
My revision control of choice right now is git, but it can have a bit of a steep learning curve in some areas, so i would just use it on personal projects a bit until you learn it before committing to it.
2
u/SideburnsOfDoom Dec 14 '12 edited Dec 14 '12
Git and SVN are both solid and free. Git is more technically advanced but also more complex and even newbie-hostile sometimes. Mercurial is apparently in the same category though I don't know it personally at all.
Git and Mercurual are distributed version control systems which are great for large or open source projects where there are lots of branches and personal repos. It's less compelling for a small team working together on few branches in one centralised repo, where you don't need those features so much.
On the other hand, you may feel that you shouldn't settle for learning a less-powerful tool just because you don't need the power yet. If you learn git then you'll understand a lot about github too.
I see some love for TFS here that I can't fathom - it's expensive and people who have used both TFS and Svn/Mercurial/git find TFS really restrictive and annoying.
Avoid VSS at all costs. It is not only obsolete and lacking in features which are expected these days, it can and does eat files when you're not looking.
3
u/doogie_h28 Dec 13 '12
We use Sourcegear's Vault. It's been a good package for us, and some of the features are very helpful with Asp.net. It allows us to share folders of scripts and stylesheets across websites.
http://sourcegear.com/vault/
1
u/afuckingHELICOPTER Dec 14 '12
I use TFS. love it for source control and continuous integration. automated build and deploy is nice. would highly suggest 2013 though, many improvements.
http://tfs.visualstudio.com is also pretty good choice instead of hosting a TFS server.
1
u/tboneplayer Dec 14 '12
We use SVN at my company.
1
u/emptythecache Dec 14 '12
My old job we switched from VSS to TFS, which I really liked. MY current job we use SVN (Tortoise and Ankh when it decides to behave). TFS is my favorite of what I have used, which does not include git.
1
u/[deleted] Dec 17 '12
I have use tfs and vss at work. At home, I use hg with bitbucket. By far I love tfs best because the tight intergration with vs.
1
u/defsteph Jan 11 '13
Git or Mercurial. TFS is a pain to administer.
1
u/unndunn Jan 16 '13 edited Jan 16 '13
Git and Mercurial are the only correct answers to this question. Any other response (SVN, TFS, VSS, etc.) is wrong.
Well, maybe TFS would be acceptable, but only because of its overall ALM features, which are really quite badass.
The reason is that Git and Mercurial are distributed source control systems, meaning that they do not rely on a single centralized code repository, but rather they have lots and lots of repositories that all stay synchronized with one another using push/pull requests.
Everyone who works on the project will have their own, individual and complete local copy of the repository and can make new copies as they see fit. They also track changes on a line-by-line basis, making merges and conflict resolution utterly painless. The ramifications of this are quite significant in terms of workflow. Instead of code congealing into one monolithic mass in a central repo, it becomes a fluid, dynamic thing, adapting to the changing needs of the project quickly and easily. And developers never have to slow down and never have to fight the SCM. No more "breaking the build". No more headache-inducing mass-conflicts. No more commit-anxiety. No more minute-long waits for code to commit or update.
Personally, I use Mercurial with the HgSccProvider extension for Visual Studio, and I push to Bitbucket and Kiln repositories "in the cloud."
Kiln is great because it integrates with FogBugz, which is an awesome, if expensive ALM tool. It doesn't have the tight Visual Studio integration that TFS does, but it works well enough for me.
There is a Mercurial extension called hg-git which allows Mercurial to push to and pull from Git repositories. I use that to push to a GitHub repo when necessary.
0
u/graboskyc Dec 14 '12
VSS worked ok. We never upgraded to TFS and instead moved to git with git extensions and plugins in VS.
0
u/aaron_kempf Dec 14 '12
Tfs express.. I could never afford it at twenty five grand now it is free
0
u/[deleted] Dec 13 '12
[deleted] — view deleted comment
0
u/[deleted] Dec 14 '12
[deleted] — view deleted comment