Last night, I presented at the Dallas C# SIG on behavior-driven development. During the conversation, SvnBridge came up, and I misspoke by saying that SvnBridge was a server-side thing. It is actually a client side proxy. Your SVN client points to the bridge, and the bridge points to TFS.
I had the good fortune to speak with Ayende recently when he was state-side and working with MS on SvnBridge, and though we talked about the bridge, I misunderstood this. D'oh.
I've used Process Explorer from SysInternals for a long time now. But, on my Vista x64 machine at home I had problems after select the "Replace Task Manager" option. Task Manager (or ProcExplorer) would no longer start from context menu of the Start bar.
After installing Vista x64 on my Dell Inspiron 1720 laptop (runs beautifully, BTW), I ran into the exact same problem. Tonight I decided to finally hunt it down. This post shows how to edit the registry to run Process Explorer in Vista.
However, unlike the instructions within, I just added my ProcExp path (unzipped to "C:\Program Files\SysInternals\Process Explorer\procexp64.exe") directly into the registry setting (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\taskmgr.exe, Debugger) without the SUDO utility. Apparently without UAC turned on, you don't need to elevate the privileges -- but ProcExp still doesn't know how to update the registry. Surgery complete and patient up and walking around.