Hi all, I've been playing around with orca for the first
time and I'm having issues trying to connect to TFS. The
workspace is setup and working fine within PB, connecting,
checking out, checking in, etc.

Within an orca script file, if I specify:
scc get connect properties "C:\PB Apps\Test\test_tfs.pbw

I get a:
Orca error in 'scc connect '. Result Code -23.
Unable to read SCC connect properties for Microsoft Team
Foundation Server MPC1\User1
An error occurred reading the Windows registry entry.

If I provide all the connect properties:

scc set connect property provider "Microsoft Team Foundation
Server MSSCCI Provider"
scc set connect property userid "PC1\User1"
scc set connect property logfile "buildfromsource.log"
scc set connect property logappend false
scc set connect property project "$/TFS/Test"

I still get the same error. Digging deeper, it looks like
orca has an issue reading the registry entry for the SCC
provider, because it can't find it, it looks up a truncated
key "Microsoft Team Foundation Server M"

If I ommit the userid property from the script, it prompts
me for the userid, effectively defeating automation, but it
does work that way. Any thoughts? it looks to me I might be
talking to sybase's tech support.

On a side note, what's the best way to setup a new pc with a
source controlled pb app? Is there a better way than copying
the PBLs from another developer/build server?

Thanks for your input.

According to Microsoft's own documentation of the SCC API, which they
created, the provider name is limited to 31 characters. The length of that
name is 48! Really nice when you violate your own standards.

Orcascript seems to be coded to handle up to 34.

You should be able to change the name in the registry editor.

Go to this key:
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders

Rename the provider value name to "Microsoft Team Foundation"

Now go to the key under HKEY_LOCAL_MACHINE that is shown as the Data for the
provider.

Find the value "SCCServerName" and change the value to "Microsoft Team
Foundation"

Now change the settings on your workspace to point to "Microsoft Team
Foundation"

Thanks for the reply. I was suspecting that I was going to
need to modify the key as well.