Geek Answers Handbook

Initial control for .Net guy

See VSS or SVN for a .NET project? , among many other similar issues.

There are many options for ASP.Net developers, some of which are complete garbage, and some are rich and expensive.

I use Visual Source Safe 2005 for a while when I am engaged in personal development, but only on my personal projects. Let me say that he has a problem.

The worst problem is that it does not seem to be able to handle ASP.Net websites. Most things are never checked when editing, no matter how you set it up, and usually I need to get the latest and say “Keep local changes and exit” to get this functionality.

In any case, I wanted to see if anyone could help me move away from this monster to something more stable. Team Foundation Server is clearly crowded. SourceVault is reliable, but curious. SVN is free, but all the plugins that most other version control providers give you make it worth something when all is said and done.

I'm just curious what everyone uses, and if they can offer a better way to go.

+6
version-control
source share
9 answers

I recently moved my team from SourceSafe to Subversion using three free tools:

You will also want to refer to the Subversion book .

It was easy to create and was a huge success. SourceSafe is a disaster - the final straw for me was when I had to combine the function branch and found that the functionality really does not exist in any usable form.

I prefer to use TortoiseSVN for complex operations like adding svn solutions, branching and merging. I use AnhkSVN to update, commit and return.

Keep in mind that the latest versions of these tools are currently built for different versions of Subversion. VisualSVN and AnkhSVN are built against 1.5.5, but TortoiseSVN is built against 1.6. You can either grab a previous version of TortoiseSVN or use the daily build of AnkhSVN.

+13
source share

I suggest taking a closer look at SVN. We made the switch from SourceSafe to SVN about 18 months ago, and I would never want to go back (we basically do ASP.NET stuff).

In particular, when working in a team, the edit-merge-commit model makes it much simpler than the SourceSafe Lock-Edit-Unlock model. In addition, the processing of fakes is much easier with the help of subversive activities.

As for the plugins, I can say the following: I mainly use TortoiseSVN (free), which is well integrated in Windows Explorer. I really don't miss the plugin built into Visual Studio.

Out of curiosity, I installed AnkSVN (free), which gives you an integrated solution (in VS). I have to say it works very well, but most of the time I still use TortoiseSVN.

+7
source share

You write a .NET guy ... if you are just one user, SourceGear Vault is free. After that, it supports about 250 USD / user with support. Anyway, I've been using Vault for years. Simple, works well and comes from Source Safe, the interface will be similar.

www.sourcegear.com

At home, I use the free single-player version. At work, we licensed about 60 users.

+5
source share

VisualSVN is great, but not free (although a community license allows free use on computers without a domain). AnkhSVN is free. Bazaar does not have much integration with VS, but it works great from the command line.

For large-scale projects, TFS is one way if you are looking for a centralized version control system.

I personally recommend switching to Git.

+4
source share

I use the free Visual SVN Server for the server side of things and the TortoiseSVN client for integration with Explorer.

I'm not worried about Visual Studio integration, as I use TVSN for projects other than VS. I also installed command line SVN tools for automatic builds using the MSBuild community tasks.

I also installed TortoiseSVN to show the “changed” icon if there is something in the tree in which it is not installed, and I ignore certain folders (for example, bin and obj ). My design tree matches my repository location.

+3
source share

If your work is so unimportant that you refuse to spend money on it, why do it at all? Bite a bullet, spend $ 50 and buy VisualSVN .

+2
source share

I went with Team System and was very pleased. Yes, it probably appeared more things than ever, but I thought: I want to spend my time setting up and maintaining a large number of free (or inexpensive) software and minimizing my own development environment or hosting my (company) on An integrated environment that our guys can support for me. I decided that my time cost a lot more to write organization code and was a good reason to invest in TFS.

Believe me, this was not a big sale to my manager, who completely agreed with me. Since the server guys already support SharePoint and SQL Server for other reasons, they don’t even put in any more effort - just another server that you can worry about from the dozens that they already support. Since we run it in a virtual machine, the hardware costs are negligible.

If I worked for myself, obviously, my calculations could be different. I would say, however, that you need to consider the costs not only of the software, but also of the amount of time (and skill) that you are willing to devote to maintaining your environment. You need to consider the opportunity costs associated with drawing bits and parts of your development environment and maintaining them when you can write a billing code.

+2
source share

SourceGear Fortress (client and server)

  • Great integration with Visual Studio
  • Solid application
  • Has a problem tracking system on board.
+1
source share

Team Foundation Server is not necessarily redundant. If your team has 5 or fewer developers, and you already have a subscription to MSDN, you can use the editorial team for free. It’s also nice to upgrade to the full version when the team gets bigger.

You do not need to use all the functions of project management if you do not want to. Using version control is fine and a big improvement over Visual Sourcesafe.

I would change the default compare and merge tools with something like Compare It! although.

+1
source share

More articles:


All Articles