What is the best practice for setting the SccAuxPath property in a Visual Basic.NET project for a distributed command?

We recently switched to Team System, and now the remote team needs access to our source. However, they use a different IP address to access the Team System server, and whenever they try to open a project, they are invited to check and change the project. Is there any way around this? This seems to be the SccAuxPath property, which is the problem.

EDIT: I found this article explaining that there are three ways to support distributed commands using TFS-VPN, a reverse proxy server, and a hosting solution. I accept Jason Whitehorn's answer by suggesting the first VPN option that seems best. If this is not possible for us, I propose a reverse proxy option.

+3
source share
2 answers

I would suggest (from the problems you have) that your remote command does not access TFS via VPN.

, TFS, , TFS. DNS IP-. DNS , IP-, .

+4

, SccAuthPath. TFS. SAK Scc. TFS, , , " " ( ? SAK? Funny TFS).

:

<SccProjectName>%24/Project/Trunk/Source/A.Library.Tests</SccProjectName>
<SccLocalPath>.</SccLocalPath>
<SccAuxPath>http://myserver:8080</SccAuxPath>
<SccProvider>{4CA58AB2-18FA-4F8D-95D4-32DDF27D184C}</SccProvider>

<SccProjectName>SAK</SccProjectName>
<SccLocalPath>SAK</SccLocalPath>
<SccAuxPath>SAK</SccAuxPath>
<SccProvider>SAK</SccProvider>
+8

Source: https://habr.com/ru/post/1722781/


All Articles