A few days ago, we posted the latest updates to the online documentation. Below is a summary of the new and updated content. Perhaps the one I’ve gotten the mote requests for is information on configuring TFS for HTTPS.
Team Foundation Administration:
|Securing Team Foundation Server||
Now you can learn about how security for Team Foundation Server is integrated with Windows authentication and utilizes permissions for users and groups. You can learn about the advantages of configuring your deployment of Team Foundation Server 2010 to use HTTPS with SSL, and follow the steps to support or require this protocol for web connections between the data, application, and client tiers.
The TF Proxy command has two purposes, and each purpose is aimed at a different type of user.
You can read more about the command in Tim’s blog post: What If Using TFS Proxy Was as Easy as Making a Get? and in the MSDN topic.
Planning and Tracking Projects
- Significant changes have been made to the content that supports defining and customizing work item type definitions. The topic node formerly titled “Work Item Type Schema Reference” has been eliminated. To learn more, check out the post Significant Changes Made to Streamline the Content for Work Item Type Schema Reference on the Visual Studio ALM Developer Content Team blog.
- You can now define data fields globally for a team project or collection using global workflow. This feature requires that you upgrade to Service Pack 1 for Visual Studio Team Foundation Server 2010. Several topics related to defining fields and global lists were updated to reflect this new feature. For more information, see Customizing Global Workflow.
- An addition was made to the Compatibility Matrix in the topic, Compatibility between Team Foundation Clients and Team Foundation Server , to clarify that you can use Team Explorer for Visual Studio 2005 Team System with Visual Studio Team Foundation Server 2010 as long as you have installed Service Pack 1 and the GDR or forward compatibility update.