TFS 2017 - Scrum Bug

Subscribe

TFS 2017

A collection of 8 posts

Connect any version of Visual Studio to Azure DevOps or Azure DevOps Server

Azure DevOps Featured

Connect any version of Visual Studio to Azure DevOps or Azure DevOps Server

Visual Studio has been around for a long time and there are still people developing in Visual Basic 6 or Visual Studio 2008. Even if you're using a more recent IDE, you could need one or more hotfixes and/or service packs.

Install Team Foundation Server Power Tools side-by-side

Team Foundation Server

Install Team Foundation Server Power Tools side-by-side

You might be connecting to multiple versions of TFS and use multiple versions of Visual Studio. Which Power tools work with which?

New versions of TFS/VSTS build tasks

I just pushed out new versions of the following tasks: * MsBuild Helper Task [https://marketplace.visualstudio.com/items?itemName=jessehouwing.jessehouwing-vsts-msbuild-helper-task] * Fixed a number of bugs when the Agent's work folder has a space in it somewhere. * Snyk [https://marketplace.visualstudio.com/items?itemName=jessehouwing.vsts-snyk] * Fixed auto-update of built-in

Clean up your Team Project Collection prior to migrating to VSTS

Team Foundation Server

Clean up your Team Project Collection prior to migrating to VSTS

To prepare your TFS Project Collection for migration, you may want to remove (stale) old data to reduce the database size first. Most actions are already documented here. Queries that can aid in detecting where your space is allocated are also found in this recent support ticket. Delete old workspaces

Make a Group Team Administrator in VSTS/TFS

Make a Group Team Administrator in VSTS/TFS

In case your organisation is depending on an Identity and Access Management tool to assign rights to the tools in the toolchain, then it's likely that all of your permissions are handled through Group assignments and not to individuals. Visual Studio Team Services and Team Foundation Server allow rights assignments

Add :8080 to your TFS 2017 bindings after upgrading to SSL

Add :8080 to your TFS 2017 bindings after upgrading to SSL

Because TFS 2017 allows authentication with Personal Access Tokens (PAT) it's recommended to upgrade to SSL if you were still on port 80. The installer will even help with the configuration and can add a redirect from port :80 to :443. It doesn't add a a redirect from port :8080

Extending your
Build and Release pipeline

Azure DevOps Pipelines

Extending your Build and Release pipeline

The new build and release engine that ships with Visual Studio Team Services and Team Foundation Server 2015 (The Release Management bits shipped with TFS 2015 update 2) provides a whole new way of configuring your Continuous Integration and Deployment pipeline. A much improved and simplified way. You may have

A quick peek into Team Foundation Server 15 Preview

Gian Maria Ricci already covered a nice overview of what's new in the install experience of TFS 15 in the latest Preview Release. [http://www.codewrecks.com/blog/index.php/2016/07/09/impressions-on-installing-tfs-15-preview/] Let's walk through the new features in the product... though I suspect that many of you