Showing archive results for June 2017

Azure functions now support creation of deployment slots, just like apps on App Service you can create slots and perform swap operations between slots.We have revamped the backup experience to make it more streamlined and easier to configure.The new Delete experience provides more information about what will be deleted and allows you to opt out of ...

With the new Visual Studio 2017 support for Azure Functions, you can now author functions using C# class libraries. With the new project type, triggers and bindings are defined using attributes, which are then converted to function.json as a build task.

Over the last few years, Microsoft has been moving the entire company to a modern engineering system built on Visual Studio Team Services and using Git as our version control system. For many of the projects within Microsoft, this is no problem, since: the Git homepage tell us: Git was built to work on the Linux kernel, meaning that it has had to e...

We first introduced basic build automation capabilities in TFS 2005 and, over the years, it has evolved substantially.  In TFS 2010, we introduced a major update which we now call “XAML build” because the build orchestration layer was based on the XAML workflow engine.  As that got adopted, we found that workflow was just not the best representati...

At Build 2017, we presented a tech talk entitled “Why You Should Use F#”. However, not everyone can attend Build, and many attendees were unable to find a position in the room where they could adequately hear us. You can see the talk for yourself in video format if you haven’t seen it already.

When you select to create custom images from a virtual machine, Azure DevTest Labs now generates the following instead of VHD files: Managed images for Sysprep'ed (for Windows)/deprovisioned (for Linux) lab VMs; Managed snapshots for non-Sysprep'ed/deprovisioned VMs.