We plan to move from Visual SourceSafe to TFS. For this purpose, we brought a new server machine with updated specifications and TFS. The Visual SourceSafe machine is still used in the environment as a TFS machine designed for a single project.
All projects are in Visual SourceSafe machine and managed since more than half a decade. As I said, there will be only one project that will be moved to the TFS machine. Here we need a complete and safe image of the working directory of the VSS project on the TFS machine, because Migrating from VSS to TFS . to install Visual SourceSafe on a TFS machine.
What is the best practice for VSS working directory (project) from machine-to-machine. Is there a way to avoid this step and we can directly move the VSS working directory to TFS?
After installing the project working directory on the TFS machine, we can use the VSSConverter.exe utility to transfer from VSS to TFS. There is a GUI version of the VSSConverter.exe utility that makes this easier than executing this command using the command line.
Team project successfully created with MSF for Agile Software Development on TFS machine. Initially, there was a problem trying to create a Team Project that did not seem to be able to start the SharePoint services. Finally, we got into some kind of blog that mentioned that after installing SharePoint services after TFS, you need to check the SharePoint Central Administration services and change its port to the default value of 17012.
This is what we could do on TFS. Not sure if we are on the right track or not? The request is not a large transfer of one project from Visual SourceSafe, which is an independent machine for the TFS machine. But, this is because we are all new to TFS.
, , Windows 2008 Server R2 TFS, , . , , , , .
, , , , . , . .
.
!