It is required to store different versions of the project and with the possibility of rollback if necessary. I don’t understand much about these version control systems, but I need something that is understandable and simple. I put VisualSVN like everything is clear and simple, but did not understand how to store different versions of the project.

    3 answers 3

    As I understand it, you need something like branches, Branch?

    IMHO, this is far from a simple thing, at least in their implementation)

    Documentation

    • Not really branches. Just store different versions for example separately 0.5, separately 0.6, etc. By the way, I need it for Visual Studio - zerpico

    VisualSVN is just an add-on for TortoiseSVN. TortoiseSVN is a client for SVN able to create its own SVN repository on disk and work with it (without the inscription of a special server software), of course, with a real SVN Server it also works. If different versions are understood as different branches of a project, then in VisualSVN there are opportunities for a project to be branched out (that is, they put a project and immediately created several of its branches, each of which, from this moment on, lives independently). If versions are understood as consecutive releases of the same project, then in SVN it is also possible to fix a certain state of the project with the possibility of rollback to this state. How this is done technically, see the dock, you can not describe everything here. But I recommend you to look either towards the Team Server (Microsoft’s native product is the successor of Visual SourceSafe) or towards Git. SVN is a slightly outdated technology. Although it depends of course on your tasks.

    • 2
      > there is nothing you can describe, but you wrote a bunch of false information. - Yura Ivanov
    • On the basis of what, by the way, did you decide that Subversion is a "slightly outdated technology"? - Costantino Rupert
    • Now many are moving with projects on git for the reason and here already the place for the whole article should be reserved and in 2 words Git, in contrast to SVN, is a distributed system. There is no center in SVN. Each developer will have his own copy of the repository with all the committees. Personally, I don’t have in SVN a built-in documentator in both Team Server and distribution as in Git. Notice, I wrote at the end depending on the tasks. A small team sitting together together SVN quite enough. Problems begin when the team grows and sits around the world. Now explain what is false information? - Mikhail Tchervonenko
    • Perhaps the outdated should be replaced by a less convenient, although outdated, in my opinion, also suitable. In general, this is holivar. Type in Google "than git is better than svn" and get enough information. ps I myself keep major projects under SVN, but this is already determined by the specifics of our team. Your personal on github. - Mikhail Tchervonenko
    • you apparently did not have to work with repositories in thousands of 5 commits and "around the world." what the superstructure is over is generally beyond the limits. the fact that they host on a githaba basically projects on three or four contributors a maximum, more often on one, as well as could be svn and any other cvs or dcvs. In the meantime, the TS asked about tags , this concept is in any system, and specifically in VisualSVN, too, strangely enough. It is strange that you did not say about it, since you are so experienced in what is there and from where. - Yura Ivanov

    Honestly, in my opinion for the studio as a Source Control it is better to use Team Foundation Server.