#vsonline

[bfcamara]

Great post explaining the new TFS/VSO Build system (vNext), particularly the improvements regarding build infrastructure management, when compared with the older approach.

[allthingsms]

Today we enabled Team Project rename on all VS Online accounts.  Team Project rename is our #1 User Voice request, by far and the longest standing customer complaint.

[3ntblog]

Visual Studio Online integration with Twitter via Zapier

I love how some indy developers tweet when they do a code push. Facepunch does this with Rust and it's cool to see the game evolve in real time. I decided to do the same for a new app I'm developing. 

I'm using Visual Studio online to track my work items and to host my code via their git support. There's a great automation site called Zapier.com that allows you to trigger actions based on events from VS Online. It was very east to setup.

Basically, I created two rules - one for web changes and another for app changes. For each of them I setup a filter so that if the word "ignore" is contained in the text the push will be ignored. That way people won't see some of my stupid commits. :) 

In just a few minutes everything was working great. I setup a specific template for each type of push in order to identify the source of the change. 

[bfcamara]

Consuming VS Online REST API using a Service Account

One of the great things about the VS Online REST API is that you no longer need to have installed Visual Studio or Team Explorer, or just the TFS Object Model to integrate with TFS. It's just a normal REST API we can consume by making HTTP calls.

Following the documentation on VS Online site, it seems that we are limited to consume the REST API using alternate credentials (basic authentication with username and password) or using OAuth (bearer access tokens).

This is not perfect if we're developing some integration work in VS Online and we want to use a Service Account to perform some tasks such as queue a build, create work items, etc.

Well, if it's possible to use service accounts when using TFS Object Model, there should be a way to use them as well with VSO REST API . In fact there is a way to use a service account in the REST API, and this post aims to show you how to do it.

First and foremost, we need to get a Service Account in VS Online. For that we can use the tool TFS Service Credential Viewer provided by Martin Hinshelwood from naked ALM. You can even watch a video explaining how to do it.

Next, in order to use these credentials with REST API, we need to understand what TFS Object Model does and try to replicate the same behavior in REST API and check if we succeed. Basically TFS OM uses OAuth WRAP Protocol to get an access token from Azure Access Control Service  (ACS).

With the help of Fiddler, here are the interactions we got when using TFS OM:

Hit VS Online unauthenticated to get a redirect 302 response where there are some headers that contain federation data, namely, realm and issuer

Request a token from ACS via the OAuth WRAP Protocol passing the Service Account username and password

Use the returned token in the Authorization header with a WRAP scheme when invoking TFS services.

Let's try to code this in C# and see what we got. If you want a full gist we can grab it from here.

Let's start with Step 1 to get federation data.

Having the federation Realm and Issuer, we can now request an access token

And finally we can use the access token to consumer our REST API, to get the list of team projects for example.

Here is the result for my account

It works!

As a side note, this method of consuming the REST API is not documented in VS Online site which means that we have no guarantees that it will still working in the future.

 I hope it helps.

[resultsofstaticcling-blog]

Online shopping's a you-know-what.

So...You're telling me that even with a $15 discount and a $10 gift card, I have to pay what my total was BEFORE tax and shipping?

Tax and shipping cost $25?!?!?!?!??!?!?!?!?!?!??!?!?!!?!?