This post covers an approach you can use to deploy compiled C# Functions using the tooling available in Visual Studio 2017 and various Build and Release Management Tasks contained in Visual Studio Team Services (VSTS). Note that this post discusses deploying to the v1 Functions runtime platform. I was lucky enough to speak with Damian … Continue reading Multi-environment deployments for Compiled C# Azure Functions with VSTS Release Management
When you work as heavily as I have with a technology like Application Insights you do tend to forget the amazing power you have at your fingertips. Over the last few years I've come to rely heavily on Application Insights as the primary Application Performance Management (APM) tool of choice for services I build, whether … Continue reading Microsoft Application Insights – APM for Everyone
I am currently transitioning some work to another team in our business. Part of this transition has been to pre-configure various Service Endpoints in Visual Studio Team Services (VSTS) to provide a way for the new team to deploy into target Azure environments without the team necessarily having direct or privileged access into those Azure … Continue reading Provide non-admin users with read-only access to Service Endpoints in VSTS
In my previous post I covered how you can move from deploying a solution to pre-provisioned Virtual Machines (VMs) in Azure to a process that allows you to create a custom VM Image that you deploy into VM Scale Sets (VMSS) in Azure. As I alluded to in that post, one item we will need … Continue reading Moving from Azure VMs to Azure VM Scale Sets – Runtime Instance Configuration
I have previously blogged about using Visual Studio Team Services (VSTS) to securely build and deploy solutions to Virtual Machines running in Azure. In this, and following posts I am going to take the existing build process I have and modify it so I can make use of VM Scale Sets to host my API … Continue reading Moving from Azure VMs to Azure VM Scale Sets – VM Image Build
If like me you’ve been a keen user of Visual Studio Online since it first came into existence way back in 2012 you’ve probably gotten used to using it with Microsoft Accounts (you know, the ones everyone writes “formerly Live ID” after), and when, in 2014, Microsoft enabled the use of Work (or Organisational) Accounts you either thought “that’s nice” and immediately got back to writing code, or went ahead and migrated to Work Accounts.
If you are yet to cutover your Visual Studio Online (VSO) tenant to use Work Accounts, here are a few tips and gotchas to be aware of as part of your switch.
The VSO owner Microsoft Account must be in Azure AD
Yes, you read that correctly.
Azure Active Directory supports the invitation of users from other Azure AD instances as well as users with Microsoft Accounts (MSAs).
If you haven’t added the MSA that…
View original post 690 more words
At TechEd North America Microsoft announced the availability of a preview REST API for Visual Studio Online. Anyone who has spent time around Team Foundation Server will know that it's always had a strongly-typed C# SDK which can be used to extract and manipulate work items held in TFS. This REST API is new and … Continue reading Retrieve Work Item Discussion History using Visual Studio Online’s REST API