Follow Us

While most teams realize integrating the development processes with the operation processes can return a ton of value –such as decreased release cycle times and much improved response times to live sight incidents most teams aren’t integrated due to the tools. With Visual Studio 2015 and Azure SDK 2.5 can now deploy your applications to an environment faster and easier than ever. This environment can then be shared across your team in VSO.

Choose the template/blueprint that suits your needs. After this, select the “Web Project” that you want to deploy. This project will then get built, and deployed onto your website.

Deploying the solution

For deploying the solution follow the steps below:

1. Right click on the Cloud Deployment Project Deploy New Deployment

2. Choose Environment. If there is an error: “Not connected to a team project” then connect to a VSO team project from the team explorer, and try deploying again.

Creating an Environment

An environment comprises of the Infrastructure on which software runs. These resources may be present on the cloud or on premise.

To deploy the solution, a website is required. The deployment project that was created earlier, also creates a sample template for the website. However, parameters need to be specified for the website. This section provisions a website and deploys the solution.

1. The required parameters are as given below:

2. Subscription: The Azure subscription, where the website will be hosted.

The Azure subscription needs to be registered with the Visual Studio Environment Service. After registering the service all the members in the VSO’s team project can use the subscription to create environments in it.

2. Name: The name of the environment, as well as the, Azure Resource Group.

3. Environment Definition: Select the deployment template that was included in the Deployment project “{SolutionName}-Paas.json”. More details about the Environment Definition is available here.

4. Location: The Azure data centre where the environment add its associated Resource group will be deployed.

5. Shared: Sharing an environment with the team, enables every member of the team to perform operations on the environment like deploy, start, stop, delete.

6. Parameters: The environment parameters are required to create the environment from the environment definition. The parameters are parsed from the Environment Definition.

2. After all the mandatory parameters have been specified, click on the deploy button.

Deployment in progress. (Behind the curtains)

1. Open the output window and select the “Deployment” tag.

2. The following sequence of activities happen when the deployment operation commences:

The deployment template is compiled to check for syntax errors. The DSC dependencies are ascertained and compiled with the deployment template.

The project is built and then uploaded to the Azure storage account. The storage account used is the one listed in the parameter: drop location.

After the upload to the storage account is complete, the Environment Service starts the provisioning and deployment of the environment.

It takes 6 to 10 minutes to compile, upload, provision, and deploy the environment.

After the deployment succeeds, the status of the environment changes to “ready”. The resources tab lists all the resources that have been provisioned for the environment.

3. Navigate to “sitename”.azurewebsites.net to verify that the website is running.

Frequently Asked Questions

A major component of the Project is the Azure CSM (Cloud Service Model) file, also known as the Deployment Template. It is a JSON file which contains details about the Azure resources to be provisioned and the binaries that go into each of the resources.

What is the difference between a Resource Group and an Environment?

Azure Resource Manager allows you to group multiple resources as a logical group which serves as the lifecycle boundary for every resource contained within it. Typically a group will contain resources related to a specific application. For example, a group may contain a Website resource that hosts your public website, a SQL Database that stores relational data used by the site, and a Storage Account that stores non-relational assets.

An Environment is a wrapper over Resource Group which lets you track activities that are performed as a part of the application lifecycle, such as builds, test runs, releases. You can also manage environments by specifying access control permissions and retention policies.

Why do I need to register a subscription with the Environment service?

When creating environments, the Environment service makes calls to Azure on behalf of the user, and hence a subscription needs to be registered first.

Who can use these subscriptions?

A subscription is registered with a team project, and every member of the team project can use this subscription.

Comments

I'd like to understand the purpose of this as well. How is this different from what was and is already functioning via the cloud services + publish method?
Also, how do you deploy worker roles via this new method?