tfs2017

We are trying to invoke the TFS 2015 REST API's from a web-page using Javascript and have a challenge in establishing valid authentication with the TFS server. We do not know how to generate a personal access tokens or an OAuth access tokens. The instruction below seem to apply more toward VSO than on-premise TFS. https://www.visualstudio.com/en-us/integrate/get-started/rest/basics How can I generate an authentication key/token? UPDATE: As on Mar 2017, the latest release of On-Prem TFS supports creating personal access tokens for all users. Using the below javascript code by @Elmar you can

I wish to upgrade my current TFS 2015.3 instance to 2017. It's not going to be quite as easy as advertised, however, due to some complicating factors. My scenario appears to be undocumented. I'll be installing a new domain controller (moving from Server Essentials 2012 R2 to Server Essentials 2016). The current OS is Server 2012 R2; I will be upgrading this as well, to Server 2016 (a clean install to a new VM). Both of these new VMs must retain the same NETBIOS names as before. The current SQL Server instance is 2014; I will be upgrading this as well, to SQL Server 2016. The SQL Server

Here is our situation-- sometimes we need to run a vNext build without needing to pull any source code from TFS server. But we don't want to change the workspace mappings. Is there a related setting simply ignore or disable the get source step in the build definition. Unlike any other task, the " Get sources " task added automatically when you create a new build definition, which is not able to disable or remove the task by right click it. Any suggestion appreciated! It's not able to directly disable/remove the Get Sources task. However, you could add a variable to achieve it: Build