At work, we use Team Foundation Server for source control. I work from home a lot, though, and external access to our Team Foundation Server isn't possible now or in the foreseeable future. I'm utterly fed up of using email/usb source control - almost as bad as no source control at all - so I was thinking about bringing the project(s) home via email or USB and committing them to a subversion server (probably on one of my own computers, although the free Subversion facilities offered by http://xp-dev.com/ might be an option: I could commit changes to there from work and pick them up from home).
Installing a local Team Foundation Server and editing the appropriate files to point to it would be possible as I have an MSDN license, but somehow I don't think that would work (and I don't even know where the address of the Team Foundation Server is stored, and I've looked in the obvious places like the ???scc files.)
I used Subversion previously for my own projects, with TortoiseSVN as the interface, but as I've got used to the convenience of being able to move and rename files from within Visual Studio I expect I would use AnkhSVN in Visual Studio, then use TortoiseSVN's Export function to get a clean copy of the project to take back to work to check in. What I'm worried about are conflicts arising from a project being managed by two source control providers. Is this even possible in Visual Studio (2008)? It gets cross enough that the Team Foundation Server isn't available when opening a project at home. Has anyone done anything similar? I know I could just try it and see how it works out, but I'd like to know in advance of any potential pitfalls.
Edit: I can't VPN into work for the same reasons I can't access the Team Foundation Server remotely. I surely would like to..