We want to get rid of Source Safe. We are running TFS and we are moving the dot.net project to TFS. Other projects are not integrated with TFS and do not require portals or any other TFS features (except source control).
Due to the unreliable product, I am worried about leaving other projects in Source Safe.
As far as I know, there are two options:
1) Create one in TFS An empty project named “VB6” (for example). Branch it for each VB6 application in VSS. This will put all VB6 applications in that subfolder. This way, all applications can be in TFS.
2) Put the dotnet project into TFS. Create a CVSNT repository and put all other VSS projects there.
3) Put the dotnet project into TFS. Will All other items remain in VSS. Run compact and repair weekly on all VSS databases.
Which option do people think is the best? Is there anyone else in a similar situation?
My suggestion is to simply use Source Control Explorer as the SCC client of TFS. It works similarly to SourceSafe GUI. Any reason why it doesn’t work?
The company I work for has more than 1,000 applications that we maintain. Many of them are old technologies, such as VB6, or poor technologies (Access).
We want to get rid of Source Safe. We are running TFS and we are moving the dot.net project to TFS. Other projects are not integrated with TFS and do not require portals or any other TFS features (except for source control).
Due to the unreliability of the product, I am worried about leaving other items in Source Safe.
As far as I know, there are two options:
1) Create an empty project named “VB6” in TFS (for example). Branch it for each VB6 application in VSS. This will put all VB6 applications in this subfolder. In this way, all applications are available In TFS.
2) Put the dotnet project into TFS. Create a CVSNT repository and put all other VSS projects there.
3) Put the dotnet project Enter TFS. Keep all other items in VSS. Run compact and repair weekly on all VSS databases.
Which option do people think is the best? Is there anyone else in a similar situation?
None of these three options make sense to me. If you want to stay away from SourceSafe and have decided to move to TFS (at least for your .NET Project), so basically what you want to ask is, is there a good way to migrate 1000’s source code of old technology to TFS?
My suggestion is to simply use Source Control Explorer as the SCC client of TFS. It works similarly to SourceSafe GUI. Any reason why it doesn’t work?