当前位置：文江博客话题详情

将 SVNBridge 与 TFS（而非 CodePlex）结合使用

发布于 2024-08-13 13:01:01 字数 495 浏览 4 评论 0原文

我正在尝试使用 SVNBridge 访问我的 TFS 服务器，以便我可以离线工作。我尝试使用基于服务器和基于客户端的解决方案。我刚刚收到返回的内部服务器 500 错误。但我不确定我是否正确连接到该网站。

我读过的有关 SVNBridge 的其他帖子似乎专门与 CodePlex 以及通过 CodePlex 特定 URL 连接到它有关。

我正在尝试连接到我自己的 TFS 服务器，并想知道如何正确设置 URL 格式。我需要为此做一些特别的事情吗？我感觉我已经尝试了一切。有人成功做过这样的事情吗？

因此，显然该问题与 TFS 2010 Beta 2 有关。正在此处跟踪该问题：

http://svnbridge.codeplex.com/Thread/View.aspx?ThreadId=77164

谢谢。

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

万水千山粽是情ミ 2024-08-20 13:01:01

不确定您是否仍在寻找答案，但我只是花了周末的大部分时间让它发挥作用，主要是通过反复试验，所以这是我学到的东西。

如果您使用的是 TFS-2010，则无法下载 zip 文件并让任何内容正常工作。相反，您必须下载源代码并自己编译。

您必须在安装了 IIS 的计算机上进行构建才能按原样使用网站项目。这就是我所做的，而不是更改项目以使用开发 Web 服务器。

如果您不再安装 VS-2008，您可以将整个解决方案升级到 VS-2010，一切都会好起来的。我什至将网站项目的目标更改为 4.0 框架，几乎没有出现任何问题。我必须卸载 TestsRequiredTfsClient 项目和 Tools.HttpSend 项目才能构建其余项目。

构建项目后，您需要执行 SvnBidge 主页上概述的几个步骤页，以便将这些位放入 Web 服务器上的正确位置。完成后，您需要调整 web.config 文件。

以下是您需要更改的 appSettings 以及需要使用的值：

<add key="LogPath" value="--directoryYouWantToKeepLogsIn--" />
<add key="DomainIncludesProjectName" value="False" />
<add key="TfsUrl" value="http://--tfsServerName--:8080/tfs/--projectCollection--" />
<add key="ReadAllUserDomain" value="--yourDomain--" />
<add key="ReadAllUserName" value="--domainUserName--" />
<add key="ReadAllUserPassword" value="--domainUserNamePassword--" />

如果您决定将网站升级到 4.0 框架，请不要忘记您需要更新应用程序池，因为它可能是作为 2.0 创建的。

现在网站已设置完毕，您几乎已完成。您仍然需要从 SvnBridge.PerfCounter.Installer 项目安装一些性能计数器。复杂化后，只需将这些位复制到刚刚安装网站的同一服务器并运行 exe 即可。

这不起作用

好吧，最后但并非最不重要的是安全性。我不使用摘要安全性，因为我的所有用户都具有 Windows 登录名，因此我启用了匿名访问，然后禁用了除 Windows 身份验证之外的所有其他形式的访问。Windows

身份验证不适用于所有用户，其中一些是远程的。查看源代码后，很明显基本身份验证是唯一可行的选择。我需要用户以自己的身份登录，然后将该用户名传递到 TFS，以便在签入完成后可以将其记录给正确的用户。

Not sure if you are still looking for an answer but I just spent the better part of my weekend getting it to work, mostly through trial and error so here is what I learned.

You CANNOT download the zip files and get anything to work if you are using TFS-2010. Instead you MUST download the source code and compile the thing for yourself.

You have to do the build on a computer with IIS installed to use the website project as is. This is what I did rather than change the project to use the development web server.

If you don't have VS-2008 installed anymore you can just upgrade the whole solution to VS-2010 and everything will be fine. I even changed the target of the website project to the 4.0 Framework with minimal issues. I had to unload the TestsRequiredTfsClient project and the Tools.HttpSend project to get the rest of the projects to build.

After you have built the project you need to follow a couple of steps that are outlined on the SvnBidge home page in order to get the bits into the right location on the web server. Once that is complete then you need to tune up the web.config file.

Here are the appSettings that you need to change and the values you need to use:

<add key="LogPath" value="--directoryYouWantToKeepLogsIn--" />
<add key="DomainIncludesProjectName" value="False" />
<add key="TfsUrl" value="http://--tfsServerName--:8080/tfs/--projectCollection--" />
<add key="ReadAllUserDomain" value="--yourDomain--" />
<add key="ReadAllUserName" value="--domainUserName--" />
<add key="ReadAllUserPassword" value="--domainUserNamePassword--" />

If you decided to upgrade the website to the 4.0 Framework don't forget that you need to update the application pool to because it was probably created as 2.0.

After you are almost done now that the website is set up. You still need to install some performance counters from the SvnBridge.PerfCounter.Installer project. After complication just copy those bits over to the same server you just installed the website on and run the exe.

THIS DIDN'T WORK

Okay so last but not least is security. I don't use the Digest security because all of my users have a windows login so I left anonymous access enabled and then disabled all other forms of access except Windows Authentication.

Windows Authentication didn't work for all of the users, some of them were remote. After looking at the source code it became clear that Basic Authentication was the only choice that was going to work. I needed the users to log in as them selves and then have that username passed into TFS so that as the check-ins are done they can be recorded to the correct user.

回复收藏 0 原文

~没有更多了~