Our current VSS works fine, but we are going to move to TFS anyway. The reasons are:
- VSS has no permission configuration, a developer can change any work item in source repository.
- VSS has no policy. Like code review before check in.
- VSS is slow. No real server behind.
But, the test result on TFS is good as we expected.
- No sharing anymore.
We figured out Microsoft is trying to promote Branching and Merging instead of simple sharing. So our cooperation code will need 3branches at least: one for DEV, one for Acceptance, and one for Production/Release. All other projects will branch the latest version of Production/Release. Until the cooperation code is merging (for us, it’s just a deploy or copying) into the Acceptance/Production/Release branch, outside developer won’t see those unstable/untested code. Fine, I like this idea. Bye bye, sharing.
- Explore client.
This is the new client for developer. If developer’s machine already has VisualStudio installed, it will become a plugin, otherwise it’s a standalone application looks like VisualStudio, but only TFS view in it.
- MSSCCI provider.
It’s needed for PB developing. For orcascript, I had to modify registry to shorten the string name, because Orcascript only can handle 34 chars in SCC name. Thanks to Ronarld Smith’s post.
scc set connect property provider “Microsoft Team Foundation Server”
scc set connect property userid “DomainName\LoginId”
scc set connect property project “$/ProjectName”
scc set connect property auxproject “http://tfs-servername:portnumber”
scc set connect property localprojpath “C:\work_dir\”
scc set connect property logfile “buildfromsource.log”
scc set connect property logappend false
There is a plugin develped by TeamPrise. Not free.
- Slow Refresh in PowerBuilder.
It seems this is a big problem for those PB+TFS developers, for me it’s 4 times slower than VSS. Why?
- CC.net plugin.
It’s available. Check the help file in CC.net.
Watch out the wrong example there: