I read this book in one week, and it’s really interesting.
This is not a book of classic TFS, its cookbook approach makes it different from others.
This treats almost every theme TFS but also on key topics of DevOps as cotinuous delivery on TFS 2015, but most also applies to VSTS.
The topics addressed are presented in the order of using TFS:
Beginning with the creation of a project team, the management of source code for TFVC and Git.
Then he addresses topics within builds, tests and Release using the latest version of Release which is integrated with TFS (then Update 2 RC1 or VSTS)
Finally the last themes are managing the TFS and TFS extension part with APIs and customization of work item form.
All subjects in the form of cookbooks respond to real issues encountered daily when using or administering TFS.
This book is therefore aimed both to administrators, developers, or even at Ops.
I recommend you buy it, read it and practice each of these cases.
Tarun Arora annonce blog post
Free chapter is available here.
we have seen in a previous article, the bases to create an extension for VSTS, that is to say, the pre-requisites and the structure of the Visual Studio solution.
But before you can use the extension remains of published step .
Publish an extension for VSTS is to:
Create VSIX package that contains the manifest
Upload this package in the Visual Studio publisher Marketplace
Publish files in a third website (as azure)
There are 2 Hosting modes of necessary files (html, js, css, …) for the extension:
Either the files are hosted in a third host such a website Azure :.
In this case
The manifest file vss-extension.json property contains the baseURI URL with https (https VSTS being, he can call a url https) of this website and does not contain the property files
Only the file vss-extension.json will be included in the package VSIX to publish
Either all files are included in the package to be published.
Lire la suite
This article follows a previous post on presentation of the the Visual Studio Marketplace and extensions, in this post we will see how to create an extension for VSTS.
Visual Studio (any version) or Visual Studio code for IDE developpment
NodeJs available here and update npm with command npm npm-g update: to create and publish the package
VSTS account: to test and use the extension:
Optional a external website hosting (like Azure web site) to create a website to host the pages of the extension
The Visual Studio project
Download the project template here, it helps to have a project with all the files that are needed for your extension and ready for publication.
After installing the project template, create a new project based on it (it is in the category typescript).
A solution is obtained with all the minimum files for extension.
Lire la suite
One of the major announcements during the Connect() event Visual Studio 2015 is the Visual Studio Marketplace that will enable the provision of extensions for Visual Studio Team Services (renamed Visual Studio Online).
For VSTS, Visual Studio Marketplace will allow the user to view and install an extension that will fit into the VSTS platform.
For the time extensions are only available for VSTS, for TFS On-premise is scheduled for update 2 or 3.
How to access to the Marketplace
Marketplace is accessible directly via VSTS account
Or via the url: https://marketplace.visualstudio.com/#VSTS
This page display the list of extensions made public, groupe by category.
Lire la suite
Le but du TFS proxy est de mettre en cache les fichiers du contrôleur de sources. Un TFS proxy peut être très utiles pour palier à un problème de bande passante pour des équipes distantes du serveur TFS.
Pour plus d’explications et le configurer voir mon article sur Dzone http://dotnet.dzone.com/articles/configure-tfs-proxy.
Pour que les Builds de TFS récuperent le code sources non pas du serveur TFS mais du cache du TFS proxy (celle ci étant plus récente le temps de la synchronisation) il faut modifier des clés de la base de registre.
Lire la suite
Cet outils contient une collection d’outils pour les administrateurs de TFS (Team Foundation Server).
Il s’intègre comme une extension à Team explorer.
Pour le télécharger :
Voici les liens de téléchargement qui dépendent de la version de Visual Studio : VS2010, VS2012, VS2013
Pour l’exécuter dans le Team explorer lancer le menu « TFS Administration Toolkit »
Ses principales fonctionnalités:
- Chercher du texte dans un fichier
- Nettoyage des pièces jointe de tests
- Voir la taille du contrôleur de sources
- Modifier les types des éléments de travail
When a developers team working on a remote site, using the TFS source controller may require bandwidth. To overcome this problem, we can use TFS proxy.
It will keep cached files and attachments test, to serve faster and free up bandwidth.
TFS Proxy is installed on a server and It is not advisable to install it on my same server as the TFS server Applicatif.
Installing and Configuring Team Foundation Server Proxy
To install the TFS proxy, you must first install TFS (same installation procedure that application tiers)
In the TFS Administration Console, click Proxy Server, and then click Configure features
The first configuration step is the choice of the collection to which it will connect.
Then the service account is chosen to use
Finally, the last step is the choice of the port and the location of cached files
Then click Next or revise until the end of the configuration
Client configuration (develloper pc)
To connect to TFS proxy server, configure its settings in Visual Studio.
On the Tools menu to Options
Select Source Control in Visual Studio Team Foundation Server
Check the Use a proxy server box … and informed the server name and port (filled during configuration)
tfs proxy visual studio