Book Image

Mastering Cloud Development using Microsoft Azure

By : Roberto Freato, Marco Parenzan
Book Image

Mastering Cloud Development using Microsoft Azure

By: Roberto Freato, Marco Parenzan

Overview of this book

Microsoft Azure is a cloud computing platform that supports many different programming languages, tools, and frameworks, including both Microsoft-specific and third-party software and systems. This book starts by helping you set up a professional development environments in the cloud and integrating them with your local environment to achieve improved efficiency. You will move on to create front-end and back-end services, and then build cross-platform applications using Azure. Next you’ll get to grips with advanced techniques used to analyze usage data and automate billing operations. Following on from that, you will gain knowledge of how you can extend your on-premise solution to the cloud and move data in a pipeline. In a nutshell, this book will show you how to build high-quality, end-to-end services using Microsoft Azure. By the end of this book, you will have the skillset needed to successfully set up, develop, and manage a full-stack Azure infrastructure.
Table of Contents (15 chapters)
Mastering Cloud Development using Microsoft Azure
About the Authors
About the Reviewer

Publishing your application into Azure web apps

Now, it's time to publish WebFrontEnd to Azure, and we need to perform three steps:

  1. Put the project in a source code repository.

  2. Create a web application.

  3. Establish a process of continuous integration.

We use Visual Studio Team Services as the source code repository. In Visual Studio 2015, right-click on the Solution Root Tree Node on its panel and then select Add Solution to Source Control. A dialog similar to the one shown as follows will open:

You can select the type of repository for the project code:

Team Foundation Version Control: Use this option if your team is always working connected, in the same place, and you need a strict control team working on the same files.

Git: Use it in every other case, mainly when the system is disconnected or distributed, or in general if you are confident with it. With open source, it is the de-facto standard as all public source code, including Microsoft open source code, published on GitHub is maintained...