SvnBridge - Use TortoiseSVN with Team Foundation Server

Project Description
SvnBridge allows you to use TortoiseSVN and other Subversion clients with Team Foundation Server. It converts the calls made by your Subversion client to the API supported by TFS.

Note: You don't need to download SvnBridge to use Subversion clients with CodePlex. Every CodePlex project automatically has a Subversion URL (e.g. https://svnbridge.svn.codeplex.com/svn).

SvnBridge acts as a bridge between TortoiseSVN and TFS. You point SvnBridge at the TFS server, and point TortoiseSVN at SvnBridge. This allows you to use TortoiseSVN with any TFS server without needing to change the TFS server in any way (no need to convince your TFS system administrator of anything!).

SvnBridge has both a client and a server version. The client version runs as an executable in your system tray, and the server version runs under IIS. The client version is quick and easy to run on your development machine, and the server version lets you set it up for multiple developers to use or to have "always on".

Give SvnBridge a try and let us know how it works for you! Feedback, issues, or suggestions can be submitted in the issue tracker.

Instructions
SvnBridge Client:

1. Run SvnBridge.exe
   1. GUI: Enter the port you want the bridge to use (defaults to 8081) and proxy settings if they are needed
   2. Command Line: Execute SvnBridge.exe <port number>
2. Using TortoiseSVN, run a checkout using the following path: http://localhost:8081/<tfs.server.name>/<projectname> (e.g. http://localhost:8081/tfs03.codeplex.com/SvnBridge)

SvnBridge Server - IIS 6:

1. Create a folder on your TFS App tier and unzip the contents of SvnBridge-Server.zip into the folder
2. Edit the web.config file
   1. Update the LogPath configuration value
   2. Uncomment the httpHandlers element in the system.web section
3. Using IIS Manager, create a new website called "SvnBridge"
   1. Specify TCP port 8081
   2. Specify path is the folder where you unzipped the contents of SvnBridge-Server.zip
4. After creating website, open the properties of the website and change the following:
   1. On the ASP.NET tab, make sure the version is set to 2.0.50727
   2. On the Home Directory tab, click the Configuration button, and click the Insert button to add a new wildcard application map. Specify c:\winnt\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll as the executable and make sure the "verify that file exists" checkbox is not checked.
   3. On the Directory Security tab, click the Edit button for Authentication and access control, and make sure only Digest authentication is checked.
5. Using TortoiseSVN, run a checkout using the following path: http://<yourwebserver>:8081/<projectname>

SvnBridge Server - IIS 7:

1. Create a folder on your TFS App tier and unzip the contents of SvnBridge-Server.zip into the folder
2. Edit the web.config and update the LogPath configuration value
3. Using IIS Manager, create a new website called "SvnBridge"
   1. Specify TCP port 8081
   2. Specify path is the folder where you unzipped the contents of SvnBridge-Server.zip
4. After creating the website, click on the Authentication icon and make sure only ASP.NET Impersonation and Digest Authentication are enabled.
5. Using TortoiseSVN, run a checkout using the following path: http://<yourwebserver>:8081/<projectname>

Current Status
SvnBridge has released its fourth version. The core source control features (checkout, update, commit, repository browser, show log) are all supported. Click here to see the current status of individual commands.

VisualSVN
If you haven't heard of VisualSVN, it integrates Visual Studio with TortoiseSVN. I've been using it with SvnBridge and highly recommend it. Open source developers can request a free license of VisualSVN here: http://www.visualsvn.com/request-license.html

Integration with CodePlex Work Items
You can visit this page for detailed instructions about how you can integrate SVN commit message and CodePlex Work Items.

Reporting Errors
If you are running into errors using SvnBridge, please use our discussion forum for help.
When asking for help, please remember to include the SVN operation that have happened, and any errors that SvnBridge might have raised.
If you are using SvnBridge with the CodePlex servers, please specify the project that you are working with.
Using the information in TracingWithFiddler can help us reproduce issues that happens against your local servers.

Future Plans
Version 5 plans include adding support for additional commands and continued bug fixes and performance optimizations.