Switch from SVN to GIT for C # development?

Question

Would you switch your C # SVN project (2-5 developers) to GIT? Does he have any advantages that give him extra effort?

I doubt it, but look for arguments for both sides.

Answer 1

Well, it really depends on how your developers work, and whether or not they are happy with the Subversion setup. You do a lot of merging and swearing about supporting Subversions bad merge, then Git will probably make your life easier.

I'm a little annoyed that many people seem to think that the main advantage of Git and other DVCS is that you can do offline development. That there is only a small side effect of the real function of having the entire repository on your local machine, so that branches, merging, etc. It can be done without accessing the server. In the case of Git, you can switch between branches in seconds when Subversion takes a few minutes.

If your developers are used to and love to learn new things, converting to Git will probably not be a problem. On the other hand, if you have developers who like and dislike when their work environment changes, you are probably better off staying in the Subversion world.

Answer 2

I moved all my work from SVN to Git for the 2 dev store. TortoiseGit works great on Windows, and the gitk tool just makes me a happy person.

You still have to get used to Git in shell mode on Windows for some tasks, but for most of your daily workflow, the Git GUI, gitk, and TortoiseSVN will get you there. The quality of the fork / merge system and local private stories to hack something quickly is very, very helpful to me. I also seem to be giving up version numbers and can push "clean" things to the central repository from my messy personal branches.

Answer 3

What made me move away from SVN was its slowness over the Internet. When the repository is only 100 ms away, simple operations, such as fixing and viewing the history of logs, are performed forever (tens of seconds). With Git, they take fractions of a second.

Work offline is also great. Once, when my university network declined, I could still perform and do continuous work on my laptop. I can push the updates to the central server some time later, when the function I was working on is complete and I have Internet access.

For open source projects, DVCS is a must because it allows new developers to launch a hacker right away, without having to give them write access to the central repository. It reduces entry for new developers to join the project.

I recently wrote a blog post about my experience converting SVN repositories to Git. This can help you if you decide to move away from SVN. Also remember that with git-svn, individual developers can use Git on their local machine, and the central repository is the SVN repository.

Answer 4

I would say no, because the GUI tools for GIT are really primitive at this point.

Svn has VisualSvn, TortoiseSvn, which makes integration with Visual Studio and Windows Explorer very smooth. The IMO “ease of use” of SVN tools far outweighs the distributed source control and the best merge functionality provided by GIT.

Now this is because I have no expectations of working on a version control project without connecting to a version control repository. If you spend a lot of time on a plane or a boat (skip it!), I would try GIT and see if there are enough command line tools.

Answer 5

You can check out why Git is better than SVN .