As part of the project that I am working on, I need to make sure that I allow the user to specify what GitHub repository they want to bind to their Visual Studio Team Services build definitions. I am using the Microsoft.TeamFoundationServer.Client library for that, but no matter what I tried, the repository just did not show up.
Did you know that as of today, the GIF sharing and hosting site Giphy is valued at over $600M? Or that Barry Schuler (yep, the guy formerly behind America Online) believes that:
“…GIFs are emerging as a format that consumers love and will be really important to advertisers as well,”
Add that to the list of statements you didn’t expect to hear in 2016.
This October marks a year since my switch from working on client software to working on the unified Microsoft documentation experience. Throughout the past year I had to learn a tremendous amount of absolutely new (to me, at least) things that totally changed my perception of what the importance of documentation is.
If you already checked out the Intro to Azure Notification Hubs post, there is some new material ready for you, that describes how to build a push notification service for Chrome, Xamarin.Android and native Android. Created by yours truly and Seth Juarez as part of the Azure Friday series, we tried to outline the easiest way for developers to get started with the service.
One of the features that I love the most about Visual Studio Team Services is the ability to build my code in the cloud. In my project I have a requirement for dynamic build provisioning, which works well. However, I recently tried to figure out how can I get the list of steps from a build definition, and was hitting a roadblock up until I got some help from Chris Patterson.