< /p>
I heard that using the SubVersion of the VisualSVN plug-in is a good choice. Has anyone done this switch before? If so, how painful is it?
Edit: We have a small group of developers, less than 10 people. We don’t need to control the source code of the network, it is only internal.
Some people are accustomed to the concept of branching and merging, but nothing is covered in the Subversion documentation.
I find that I often use TortoiseSVN Windows Explorer is integrated to complete most tasks, such as updates and submissions, but VisualSVN integrates well with IDEs and is good value for money.
We have used Visual Source Safe 6.0d has been around for a while, and it has been very helpful to us. However, when trying to upgrade to SourceSafe 2005, we found that it needs one leg and one leg! In addition, it does not seem to be a painless upgrade. That is, we want a different solution at a lower cost (without free). As long as it has Visual Studio integration, it will work for us.
< /p>
I heard that using the SubVersion of the VisualSVN plug-in is a good choice. Has anyone done this switch before? If so, how painful is it?
Edit: We have a small group of developers, less than 10 people. We don’t need source code control over the network, it’s just internal.
We are also long-term users of Visual SourceSafe 6, and switched to VisualSVN/TortoiseSVN 6 months ago, we have never looked back. Our team of 4 developers provides additional productivity and flexibility.
< /p>
Some people are used to the concept of branching and merging, but nothing is covered in the Subversion documentation.
I find that I often use TortoiseSVN Windows Explorer integration for most tasks, such as updates And submit, but VisualSVN integrates well with IDE and is good value for money.