Geek Answers Handbook

MS Team Foundation Server in Distributed Environments - hint tips

Is there anyone using Team Foundation Server on a team that is geographically distributed? We are in the UK, trying to work with a team in Australia, and we find it pretty tough.

Our main two questions:

  • Things are checked for us without us, asking to get the latest.
  • Even when using a proxy server, most things will take some time.

Many really annoying little things like this strengthen our arteries, stopping us from delivering the code and frankly creating a user experience similar to pushing gold syrup onto a sand dune.

Does anyone out there actually use TFS in this way daily with (relative) success?

If so, do you have any tips, tricks, tricks or gotchas worth knowing?

PS Upgrading to CruiseControl.NET is not an option.

+5
source share
3 answers

Definitely upgrade to TFS 2008 and Visual Studio 2008, as this is the version of Team Team v2 in every way. Eliminates many small and medium problems.

As for "things that are randomly checked," this is almost always due to the fact that Visual Studio decides to edit files on your behalf. Try to get the latest information from Team Explorer, and nothing is open in Visual Studio, and see if this behavior persists. I bet it won't be!

TFS - . , , GET. , TFS - , , "" .

, , , - , .

+2

TFS - , VPN.

. ( ). add-in, .

, :

  • ( )

[edit] OK , . , , VS " ", , sln proj . , ( , , ? > > )

-, - , ( ), , . ?

- , , ?

+1

In my opinion, you can have several TFS application servers in different places. They can either talk to the same SQL Server or use SQL Server mirroring. Having your own local TFS server is likely to speed up development time.

0
source

More articles:


All Articles