Tuesday, January 15, 2008

What is new in TFS 2008: More Details - Part2


Continuous Integration builds –Supports the creation of build triggers that allows you to configure exactly when Continuous Integration builds should be started. For example, you can set a trigger so that every check-in starts a build, or you can set up a rolling build so that builds will start no more often than every X minutes.
Support for build queuing –Supports build queuing and queue management. This is especially useful for Continuous Integration as multiple check-ins may queue up multiple builds.
Scheduled builds –Supports scheduled builds, which can be configured to start at specified times based on your organization’s requirements.
Drop management –Supports drop management, which gives you the ability to set policies for when builds should be automatically deleted.
Specify build properties - Allows you to specify what source and versions of source should be built along with other build properties for a build type. There are many more exposed properties for customizing a build. Additionally, MSBuild command-line parameters can be passed when queuing builds.
Extensibility of build targets –Improves extensibility of the build targets. For example, you now have the ability to easily execute targets before and after each Visual Studio solution or project is built.
Build management –Allows you to stop and delete builds from within Visual Studio.
Build configuration –Simplifies the ability to specify what tests get run as part of a build.
Build project file location flexibility –Provides the ability to store the MSBuild project file (and its associated rsp file) anywhere in the version control hierarchy instead of forcing the use of the TeamBuildTypes folder.
Support for GUI tests – Allows running graphical user interface (GUI) tests as part of the build.
Check-in Policy – Supports a new check-in policy, which prevents users from checking-in code when a Continuous Integration build is broken.
Managing build server – Improves ability to manage multiple build machines.
Workspace mapping – Build definition can be associated with a "real" workspace, meaning code from multiple team projects can be retrieved, client mappings can be specified, etc. Working folder mappings will be managed in the GUI instead of in workspacemapping.xml

Thursday, January 10, 2008

What is new in TFS 2008: More Details - Part1

Microsoft Visual Studio 2008 Team Foundation Server(TFS 2008) introduces a number of new features and capabilities. The primary changes have been:

•Administration, Operations & Setup. Installation has been simplified to reduce setup time and improved to support more deployment scenarios.

•Build. Build includes Continuous Integration, scheduled builds, and build queuing solutions out of the box. Build management and extensibility has been simplified with more functionality available from the UI.

•Version Control. Version control includes much better support for offline work and has improved performance.

•Work Item Tracking. Work item tracking includes an improved query builder and improved support for work item attachments.
These product changes are listed and briefly described below, followed by a table explaining how the changes will impact the guidance in this guide. Use this chapter to aid in your Microsoft Visual Studio Team Foundation Server upgrade planning.

1-Administration, Operations & Setup

•Simplified installation –Installation is made easier and quicker compared to Visual Studio 2005 TFS. Improvements include the elimination of the separate data-tier installation as well as the elimination of the domain account requirement. Team Foundation Server 2008 supports built-in machine accounts (such as Network Service) wherever possible.

•Support for SharePoint 2007 –Adds support for SharePoint 2007 and Windows SharePoint Services 3.0. Team Foundation Server 2008 will support SharePoint on a separate server from the Team Foundation Application Tier Server.

•Support for Windows Server 2008 – Supports the next version of Microsoft Windows Server™; for example Microsoft Windows Server 2008 and Internet Information Services (IIS) 7.0.

•Support for X.509 Client Certificates – Supports the use of X.509 client certificates to improve authentication security.

•Large group synchronization –Improves performance and robustness and will be able to support large numbers of users — approximately 30,000 or more users in a single instance of TFS.

•Support for SQL named instances –Allows sharing of a SQL Server between multiple TFS instances, or with other applications. This allows different instances of TFS to use the same installation of SQL Server 2005.

•Support for non-default ports – Improves configurability to support alternate Web sites and ports