NotAllAboutCode

For those who are not familiar with Microsoft Azure , it is a cloud computing platform and infrastructure designed for building, deploying, and managing applications and services through a global network of Microsoft -managed data centers. It provides SaaS , PaaS and IaaS services and supports many different programming languages, tools and frameworks, including both Microsoft -specific and third-party software and systems. Here are some useful resources when working with Azure . Azure Icon Set To have consistent documentation for your presentations and diagrams, you can use the following symbols: Microsoft Azure, Cloud and Enterprise Symbol / Icon Set - Visio stencil, PowerPoint, PNG, SVG Azure Services Status Azure Service Status page. Visual Studio Team Services Status page. Architecture & Best Practices Azure Architecture Center Azure Application Architecture Guide Architecture blueprints Azure solution architectures Azure reference architec

CI ( ContinuousIntegration ) and CD ( Continuous Delivery ) are nowadays solid best practices in Software Development , aimed at reducing at a minimum the risks involved with releasing software. The idea is simple: the more often you release your software, the more chances are you won’t bump into deployment issues (ie: problems during the release). Microsoft TFS ( Team FoundationServer ) has been used for long to address this needs, but since a few years (in particular since CloudComputing and Azure became a trend), it has gradually been replaced by its online version VSTS ( Visual Studio Online Team Services ). While setting up CI and CD in VSTS is not rocket science, it helps to know some basic concepts before starting. To start setting up Continuous Integration , you need to access the Build & Release tab in your VSTS instance. NOTE : One important thing to keep in mind is that Build and Release are separate activities, and to have