- can build one build definition from a single Team Project at a time.
- can build multiple build definitions from different Team Project.
- has the capability to use multiple CPUs to build projects in parallel and therefore speed up your builds.
- This multiproc feature can be leveraged in your Team Builds.
Thanks Grant for pointing out those facts.
Are you concerned about performance?
You can scale out by…
- installing a TFS proxy which will cache all version control downloads and therefore reduce the load on your TFS app tier.
- splitting your single-server TFS installation in an separate application tier and data tier (dual-server-configuration).
- moving the data warehouse (SQL Server Analysis Services) database to a separate server.
Or scale up by…
If one of the following action are planned you should ready the appropriate documentation:
- Check the Windows Event Log.
- Run TFS Best Practices Analyzer.
(part of the Power Tools, requires PowerShell to be installed first)
- TFS-Team Explorer 2008 Troubleshooting Guide (@ MSDN Forums)
- Have a look at the available troubleshooting documentation on MSDN:
- For connection trouble have a look at:
Troubleshooting connections to TFS
Since you can only deploy one master TFS server and replication mechanisms are not supported you might consider using a TFS Proxy server, which caches the downloads from the Team Foudation Version Control.
Functionality / What it does:
Cache downloads from Version Control only. Control Messages and other artifacts like work items are still transferred directly between client (Visual Studio) and server (TFS).
Read more about how the proxy works.
From a licensing perspective the TFS Proxy costs you one (additional) TFS license.
See also: Licensing whitepaper.
You find the installation files on your TFS CD under Proxy\setup.exe.
After the installation is complete you need to modify the configuration file.
See also: hardware requirements.
More Information (including all links mentioned above):
Well if you asked me a year ago if Microsoft is going to deliver UML tools the answer would not been to positive.
As you can read in Cameron Skinner‘s blog Microsoft changed it’s views a bit. It’s not anymore about “DSL vs. UML”, but a combination of both: “the right tool for the right job”.
There will be a clean separation between the two approaches:
- UML will be used at the high-level modeling (“logical” layer”)
- DSL at the “physical layer”
As a result Microsoft will introduce five UML 2.1 compliant UML diagrams with the next version of VSTS and a few new DSLs. The UML diagrams are:
- Class Diagram
- Use Case Diagram
- Component Diagram
- Sequence Diagram
- Activity Diagram
You can have a look at those on these screenshots by MVP colleague Willi.
So Microsoft is not at all moving away from DSL, but recognized the value of UML as an addition and now clearly propagates the value in using a combination of both.
The future is: UML + DSL. The “programmatic approach” as Cameron puts it.