Printable View
Have anyone used Microsoft Visual sourcesafe 6.0? What do you think about it. Is it accurate? Can you please send me your opinion about it becuase our company will use it in the next project. our next project is big and needs more than one person to touch the files at the same time, so is Microsoft Visual sourcesafe 6.0 good for our need. Thanks for your response in advance.
I know this is probably too late for you but here is my views.
Advantages :
- Cheap (comes with Visual Studio)
- Fairly easy to use (You put it in and take it out)
- Can be programmed via dll (allowing for backend work)
- Can create multiple databases
- Hooks directly into VC++ and VB allowing you to maintain
source control through your development environment
Disadvantages :
- Cannot provide application wide releases
- Can get confusing with comments and the like
- Doesn't allow for alternative version numbering
So the bottom line is that if you just want a place to store code and only have one person work on a particular file at one time (but multiple people can work on multiple different files) then you will get away with using VSS.
If however you need to use a repository and source control mechanism for part of a large company including the ability to have Application Releases (ie Release v1.2 contains code1.frm (v1.0) and code2.frm (v1.2) and code3.frm (v2.0)) then you are wasting your time here... think of something like ClearCase.
You do have the ability to do version control in VSS...I've used VSS and it isn't too bad
Not PROPER version control.
Sure you can control the VSS versions that are created but that is at a component level only...
What I am talking about is being able to do PROGRAM level Version Control which VSS just doesn't handle. It is basically a glorified repository for changing code... it isn't a development tool that allows for a fully integrated and easy to manage application revision system.
Once you branch your app in VSS, you have your different versions right there