All geek questions in one place

Why don't version control systems have Visual Source Safe sharing features, and which control source are you using, and you think it's worth a try?

We are looking for a version control system to change our current source of security. We use it together with Visual Studio. We still have not managed - and the main reason for this is that all the alternatives that we see do not support one or more VSS functions, especially the one that we widely use - the proportion of files! What's up with that?

Alternatives such as Source Gear require their support, but I must tell you that they do it very badly. Not to mention the fact that they are slower than Source Safe, and have even more errors.

What alternatives do we have for source version systems that support file sharing? Or is there a reason not to use such functions? Share your experience and support your comments.

EDIT:

Porting the file I mean that I can check the file from any project that uses it, make some changes, and then get the latest version. This is very useful when working with projects in C ++ or even with C # web projects. I want to have access to the file without having to create another library for it.

+3
source share
5 answers

From MSDN :

Sharing Files or Projects

Visual SourceSafe Share, . . .

Visual SourceSafe , . , . , , "" .

Visual SourceSafe . , Visual SourceSafe.

, . :

, . , , ( , Maven Ivy )

+5

Subversion ( , ) svn: external.

1.6 .

Git "" - , .

+3

StarTeam .

0

, , " ", , , Mercurial Git. Windows Explorer Visual Studio .

For specific features such as VSS-style file sharing, I suggest setting up a Continuous Integration environment like TeamCity and setting it up accordingly.

This is a steep curve at first, but amazing and time-efficient when your employees and servers know what to do.

0
source

Source: https://habr.com/ru/post/1718804/

More articles:


All Articles