Microsoft Team Foundation Server 2017

Microsoft Team Foundation Server 2017

What's New

Code Search

Code Search provides fast, flexible, and accurate search across all your code. As your codebase expands and is divided across multiple projects and repositories, finding what you need becomes increasingly difficult. To maximize cross-team collaboration and code sharing, Code Search can quickly and efficiently locate relevant information across all your projects.
From discovering examples of an API's implementation, browsing its definition, to searching for error text, Code Search delivers a one-stop solution for all your code exploration and troubleshooting needs.
Code Search offers:

• Search across one or more projects
• Semantic Ranking
• Rich filtering
• Code collaboration

Package Management
Packages enable you to share code across your organization: you can compose a large product, develop multiple products based on a common shared framework, or create and share reusable components and libraries. Package Management facilitates code sharing by hosting your packages, sharing them with the people you select, and making them easily accessible to Team Build and Release Management.
Package Management eliminates the need to host a separate NuGet server or file share by hosting NuGet packages directly in your Team Foundation Server. It has best-in-class support for NuGet 3.x as well as support for NuGet 2.x legacy clients. It works seamlessly with your existing TFS infrastructure, teams, and permissions, so there’s no need to deal with synchronizing identities, managing groups in multiple places, etc. It also integrates easily with Team Build so you can create and use packages in continuous integration workflows.

Agile Improvements
In Team Foundation Server 2017, we've added new features and functionality to work items and Kanban boards.
New Work Item Form
The new work item form has a new look and feel. It also adds some great new features:
A rich work item discussion experience.
Drag and drop support for attachments.
Improved history experience (History & auditing).
Improved code and build integration.
State coloring.
Responsive design.

More About Microsoft Team Foundation Server 2017

Known Issues

This is a complete list of known issues in this release.

There are no Power Tools for Team Foundation Server 2017

• Issue:

  No Power Tools have been released for TFS 2017.

• Workaround:

  We are excited to let you know that most of the previous Power Tools have been integrated into TFS 2017. The Process Template Editor is one that has not been integrated, but we are going to publish a Process Template Editor tool for TFS 2017 to the Visual Studio Gallery shortly after TFS 2017 is available. We will provide the link here as soon as it’s published.

Updating custom control extensions

• Issue:

  The schema for fields on the work item form has changed. The documentation for custom control extensions also changed.

• Workaround:

  See the new documentation

Error when importing work item type definition

• Issue:

  Customers with a work item page extension installed, who export a work item type definition then import that definition, will see an error, “The ‘LayoutMode’ attribute is not declared”.

• Workaround:

  There is an extra LayoutMode attribute on the PageContribution element each time you export a work item type definition. Before importing the definition, search for the PageContribution mode and remove the LayoutMode attribute. For example, remove LayoutMode="FirstColumnWide".

Customers should update to Git LFS version 1.3.1 or higher

• Issue:

  Git LFS versions before 1.3.1 will not be supported in future releases.

• Workaround:

  Customers using Git LFS are strongly encouraged to update to Git LFS version 1.3.1 or higher. Older versions of the LFS client are not compatible with authentication changes in this version of TFS. In order to give customers time to migrate, we implemented a short-term workaround for RTW. The workaround will be removed in Update 1, at which point Git LFS clients below 1.3.1 will no longer work.

NuGet Restore is not finding packages that exist in nuget.org

• Issue:

  When using NuGet 3.4.3 or greater, the NuGet Restore task will not restore packages from NuGet.org unless it is an explicit source in the NuGet.Config.

• Workaround:

  Ensure NuGet.org is in NuGet.Config.

NuGet build and release tasks do not authenticate

• Issue:

  When using Team Foundation Server / Package Management, NuGet build and release tasks will not authenticate to feeds if the agent is running as a NETWORK SERVICE user, which is the default when the build agent is run as a service. This happens because versions of NuGet before 3.5 use the credentials of the user account running the build agent, not the credentials provided by the build task.

• Workaround:

  To use NuGet build/release tasks with TFS feeds using an agent that is running as a NETWORK SERVICE, you must use NuGet 3.5 or higher.

NuGet build and release tasks use agent’s credentials

• Issue:

  Versions of NuGet before 3.5 use the credentials of the user account running the build agent, not the credentials provided by the build task. This may result in unexpected access or lack of access to feeds.

• Workaround:

  Use NuGet 3.5 or higher on TFS build agents.

External extensions do not automatically upgrade when upgrading TFS

• Issue:

  If you downloaded an extension from the Visual Studio Marketplace, published it to your TFS 2015 installation, and then upgraded to TFS 2017, the extension will not be automatically updated when new versions of the extension are published to the Marketplace.

• Workaround:

  After upgrading to TFS 2017, uninstall the extensions you had installed in TFS 2015. Then reinstall the latest extensions. In TFS 2017 we added a feature to automatically check for updated external extensions once a day and upgrade them.

The Jenkins Queue Job task cannot be run in release definitions

• Issue:

  When running the Jenkins Queue Job task in a release definition, customers get a 500 server error.

• Workaround:

  Currently, the Jenkins Queue Job task can be run as part of TFS build definitions, but not release definitions. This ability will be added in a future release.

Custom TFS server plugins need to be rebuilt against TFS 2017 DLLs

• Issue:

  Custom TFS server plugins do not work after upgrading to TFS 2017.

• Workaround:

  Rebuild your custom server plugins against the TFS 2017 assemblies.

The Server Object Model for Custom TFS server plugins has changed since TFS 2015 RTM

• Issue:

  Custom TFS server plugins do not compile.

• Workaround:

  Fix up source code as described

When using administrator actions, an exception is thrown

1. Issue:

   In the Alerts Administration page, when Team Administrators use the Find Alerts for a specific user search to find subscriptions for a team, they might get an exception.

2. Workaround:

   • Option 1: Click on the All Alerts node and set the All My Teams Alerts filter to show. This will show all alerts for all groups that the user has access to.
   • Option 2: In case the group is a team, instead of searching by team name, navigate to this team’s Alerts Administration page to manage subscriptions.

Thanks To WZOR

Microsoft Team Foundation Server 2017 MSDN Direct Download ISOs

Microsoft Dynamics NAV 2017 (MSDN)