Easy to use svn-client alternatives for Visual Studio?

Question

Our development team uses VS.NET for application development and TortoiseSVN / VisualSVN for version control. It seems like almost every day there are problems with a working copy or repository, and people just throw their hands and call me when this happens. There are certain human factors at work (SVN works as it should), but I'm tired of playing SVN support for the development team. Can anyone recommend a better / more intuitive tweak for version control?

Answer 1

SVN is about as simple as version control systems. Problems only arise when working with merge processes ... it can be difficult.

If you do not address the "human factors", no matter what version control system you use, you will always be a support service. To solve these problems, you usually need to:

• Set up wikis with common “recipes” for version control tasks.
• Include a workflow diagram of how changes are made to your code (for those who don't like reading).
• Have a training session that is specifically designed for your users (use the wiki material).
• When helping someone with a problem, be sure to get them to perform the actual fix. Don't just do it for them, tell them about it.
• In the process of assisting users, it is recommended that users indicate product documentation.

The introduction of a new version control system in any organization should include the elements I have listed. I understand that this is an additional work for those who do this, but it saves you from long “supportive” hours in the future.

Answer 2

The SVN agent works well for me. It goes well with Visual Studio.

Answer 3

Can anyone recommend a better / more intuitive tweak for version control?

it's better? Yes. More intuitive? This is debatable. Take a look at distributed version management software, namely Mercurial or Git. Both have freely available plugins for integration with Visual Studio. And if you manage to spend some money, I heard very good things about Fog Creek Kiln.

As for your problems with SVN, I have some tips. First, make sure that you all synchronize with the same version of the product. It is often updated, and therefore it can be difficult, since you also do not want to be too far behind the current version. Secondly, we had big problems with Tortoise trying to cache icon overlays on mapped network drives. There is an option that you can turn off somewhere that suddenly made things more stable. But that was at my last job, and I no longer remember the exact setting.

Answer 4

I think that you have already answered in your question - to understand the "human factors" by providing appropriate training. Version control for software development is not much simpler than SVN, so from the way your question is formulated, I assume that human factors will simply find other ways to make your life interesting.

Answer 5

If you are having trouble creating your repository (for example, committing tags, incorrect commit messages ...), one of the easiest ways is to do it hard: point the lock to the server to enforce policies. You can see the official documentation .

Basically, this is an easy way to provide naming / formatting and avoid many human problems (commit tags, mess with external ones ...)