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.
If you’ve used Instagram before, you’ve surely noticed how it handles DMs when shared from the home feed.
One of the key parts of my job as a Program Manager on the docs.microsoft.com team is to assess community contributions across different documentation repositories and areas. That might appear to be a very complicated task, and as we go, I will document more on the process. This post, however, is dedicated to setting up the core environment to make the task somewhat easy.
Depending on your project, you might need to run the latest version of the .NET Core SDK on your hosted build agent. Hosted agents are pulled from the VSTS hosted pool. With great flexibility comes great responsibility, so the build agent has some limitations when it comes to picking the software that needs to be deployed.