SvnBridge Wiki & Documentation Rss Feed

New Comment on "Work Items Integration"

pflugs — Mon, 01 Apr 2013 17:54:49 GMT

I tried modifying my settings the way JasonMcF described above, and I found that I was still getting errors. After doing an update to a Work Item (Bug) manually using Visual Studio and tracing the request/response using Fiddler, I realized that I needed additional columns in the XML. Once I added these columns in the XML to match the request I trapped using Fiddler, the next commit using Tortoise --> SVNBridge --> TFS closed the Bug without error. However, I then discovered that the required columns are different for different types of Work Items. I was able to configure the SVNBridge XML files to work smoothly when resolving Bugs, but the settings did not work when trying to edit Tasks. After downloading the SVNBridge code and looking through it, I believe the TfsWorkItemModifier class would need to be modified to allow for different XML configurations for different Work Items. The code in that class looks pretty straight-forward, so I might take a stab at modifying it to support this User Story sometime in the future. However, it's easy enough to manually close tickets and associate them with changes using Team Explorer, Visual Studio Source Explorer, etc., and the feature I was REALLY after was simply connecting TortoiseSVN to TFS, which works just fine. I'll put this on my "Friday afternoon" work list... ;-)

New Comment on "UnitTestingNotes"

am42 — Wed, 02 May 2012 12:45:57 GMT

I cannot figure out how these tests are supposed to be run (missing documentation). At least as of 2012, there's a SvnBridge.msbuild file in solution root which defines all relevant targets. However, trying to run msbuild SvnBridge.sln /t:ProtocolTest (in a "Visual Studio Command Prompt (2010)" shell!!) errors out, thus I'll need some more time to try to figure out The Right Thing.

New Comment on "Documentation"

am42 — Wed, 02 May 2012 11:28:30 GMT

This main Documentation link (Wiki page) is missing links to many important pages (see the Wiki history for details, currently available at http://svnbridge.codeplex.com/wikipage/history ): - http://svnbridge.codeplex.com/wikipage?title=Current Feature Status - http://svnbridge.codeplex.com/wikipage?title=Setting up development environment - http://svnbridge.codeplex.com/wikipage?title=UnitTestingNotes

New Comment on "Documentation"

leixussw — Wed, 25 May 2011 18:06:47 GMT

is this always connecting to "defaultcollection", THERE IS NO WAY TO ADD team collection in the url?

New Comment on "Documentation"

lmemmott — Fri, 01 Apr 2011 14:13:22 GMT

Suggestion: Add documentation explaining how to deal with "Team Project Collections", a new feature in TFS2010.

New Comment on "Documentation"

lmemmott — Fri, 01 Apr 2011 14:12:34 GMT

Suggestion: Add section to this page explaining the versions of TFS that SvnBridge works with.

New Comment on "Documentation"

lmemmott — Fri, 01 Apr 2011 14:12:29 GMT

<b>Suggestion: Add section to this page explaining the versions of TFS that SvnBridge works with.</b>

New Comment on "Documentation"

lmemmott — Fri, 01 Apr 2011 14:12:08 GMT

Suggestion: Add section to this page explaining the versions of TFS that SvnBridge works with.

New Comment on "Documentation"

lmemmott — Thu, 31 Mar 2011 22:43:52 GMT

It appears that the default has now changed to port 8080.

Updated Wiki: Documentation

jwanagel — Thu, 30 Dec 2010 23:31:42 GMT

SvnBridge Client:

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>
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:

Windows 2008 R2 - IIS 7:

Create a folder on your TFS App Tier machine and unzip the contents of SvnBridge-Server.zip into the folder (e.g. C:\SvnBridge\Web)
Edit the web.config and update the LogPath configuration value
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
After creating the website, click on the Authentication icon and make sure only ASP.NET Impersonation and Digest Authentication are enabled (disable all other authentication options).
Using TortoiseSVN, run a checkout using the following path: http://<yourwebserver>:8081/<projectname>

IIS 6:

Create a folder on your TFS App tier and unzip the contents of SvnBridge-Server.zip into the folder
Edit the web.config file
1. Update the LogPath configuration value
2. Uncomment the httpHandlers element in the system.web section
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
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.
Using TortoiseSVN, run a checkout using the following path: http://<yourwebserver>:8081/<projectname>

Updated Wiki: Home

jwanagel — Wed, 03 Nov 2010 01:25:10 GMT

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.

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.

Updated Wiki: Documentation

jwanagel — Wed, 03 Nov 2010 01:24:56 GMT

SvnBridge Client:

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>
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 7:

Create a folder on your TFS App tier and unzip the contents of SvnBridge-Server.zip into the folder
Edit the web.config and update the LogPath configuration value
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
After creating the website, click on the Authentication icon and make sure only ASP.NET Impersonation and Digest Authentication are enabled.
Using TortoiseSVN, run a checkout using the following path: http://<yourwebserver>:8081/<projectname>

IIS 6:

Create a folder on your TFS App tier and unzip the contents of SvnBridge-Server.zip into the folder
Edit the web.config file
1. Update the LogPath configuration value
2. Uncomment the httpHandlers element in the system.web section
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
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.
Using TortoiseSVN, run a checkout using the following path: http://<yourwebserver>:8081/<projectname>

New Comment on "Current Feature Status"

bojinx — Mon, 14 Jun 2010 21:27:18 GMT

Really need Merge, I have no way to tell everyone using my project to re-checkout again and thats kind of unfair on them. Thanks

New Comment on "Current Feature Status"

jrummell — Sun, 24 Jan 2010 16:39:01 GMT

Branch/tag and Merge would be extremely helpful.

New Comment on "Current Feature Status"

plillevold — Wed, 23 Sep 2009 07:58:21 GMT

I vote for "Branch/tag". This is extremely important, imo for every source control system.

New Comment on "Current Feature Status"

gedmurphy — Thu, 17 Sep 2009 12:20:35 GMT

Has anyone considered implementing TFS functionality somehow? Shelve would be a very welcome addition, possibly best done via a new shell extension specific to svn bridge

New Comment on "Work Items Integration"

JasonMcF — Tue, 11 Aug 2009 09:09:56 GMT

See http://www.codeplex.com/SvnBridge/WorkItem/View.aspx?WorkItemId=9889 may be the solution to your problem. The main cause of the problem is that the default template object references are the ones used by CodePlex. I was able to get the linking working by modifying the file AssociateWorkItemWithChangeSetMessage.xml and copying it locally to where SvnBridge.exe is located. I replaced CodePlex.UpdateBy with System.ChangedBy (this will be dependent on the project template you are using). The file can be retrieved from the Codeplex repository (SvnBridgeLibrary.Infrastructure.Messages).

New Comment on "Current Feature Status"

Custa — Fri, 15 May 2009 04:49:47 GMT

Is there any idea when Get Lock and Release Lock maybe be looked at? This is vital to the SVN Client I use (Axure).

Updated Wiki: Home

jwanagel — Sat, 02 May 2009 21:34:22 GMT

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>
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:

Create a folder on your TFS App tier and unzip the contents of SvnBridge-Server.zip into the folder
Edit the web.config file
1. Update the LogPath configuration value
2. Uncomment the httpHandlers element in the system.web section
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
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.
Using TortoiseSVN, run a checkout using the following path: http://<yourwebserver>:8081/<projectname>

SvnBridge Server - IIS 7:

Create a folder on your TFS App tier and unzip the contents of SvnBridge-Server.zip into the folder
Edit the web.config and update the LogPath configuration value
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
After creating the website, click on the Authentication icon and make sure only ASP.NET Impersonation and Digest Authentication are enabled.
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.

New Comment on "Work Items Integration"

alexander123 — Wed, 29 Apr 2009 11:41:04 GMT

Doesn't work. SvnBridge v4, TFS 2008. Error: Failed to associate work item with changeset. See for details: http://www.codeplex.com/SvnBridge/WorkItem/View.aspx?WorkItemId=10513