01-developer-environment

Developer Environment (.NET)

Overview

In this lab, you will set up an Office365 trial subscription, an Azure trial subscription, configure your Azure subscription for the DevCamp, and provision a virtual machine in the subscription to use for development of further labs.

Objectives

In this hands-on lab, you will set up an Office365 developer subscription, and Azure trial subscription, and an Azure-based virtual machine for the development environment for subsequent labs in the DevCamp. To expedite the process, we've prepared a Windows image that you will copy into your own environment, start the virtual machine and connect to it. You will then configure the components for Azure development.

• Set up an Office365 trial subscription.
• Set up an Azure trial subscription.
• Configure your Azure subscription for DevCamp.
• Create an Azure Virtual Machine for remote development.
• Connect to the Azure Virtual Machine and configure it for development.
• Review the features of the Azure Portal.

Prerequisites

You will need a cell phone and credit card for identity verification.

The credit card will not be charged unless you remove the spending limit on the subscription you will create.

Exercises

This hands-on-lab has the following exercises:

• Exercise 1: Set up Office 365 trial subscription
• Exercise 2: Set up Azure trial subscription
• Exercise 3: Start your VSTS trial subscription
• Exercise 4: Configure your Azure subscription for DevCamp
• Exercise 5: Use an Azure Virtual Machine for remote development
• Exercise 6: Deploy Shared API application
• Exercise 7: Azure Portal walk-through
• Exercise 8: View the resources you created

---

Before you start

🔺If you already have an Office 365 subscription, please use an alternate browser or use private mode! This will help avoid any issues with conflicting accounts.

Clear your browsers cache and restart your browser.

Do not skip exercise 1! Even if you already have an Office 365 subscription and address, follow exercise 1 and create a new account.

Use the account created in exercise 1 for all the following exercises and hands-on labs!

To register for a free trial use an e-mail address and a phone number that has not been used for a free trial yet!🔺

---

Exercise 1: Set up Office 365 trial subscription

1. In your browser, go to products.office.com/en-us/business/office-365-enterprise-e3-business-software and click the link that says Free Trial.

   

   This will navigate you to this page:

   

2. Enter the information requested, and click Next which will take you to the following page:

   

3. Choose a user id and a tenant name for your trial. In this case I chose devcampross, but you can choose anything you'd like, as long as it is unique. You'll also have to choose a password, and click Create my account.

4. Next you will see this page, which asks for phone verification:

   

5. After this process is complete, your O365 trial will be set up, and you'll see this page:

   

   Make note of your user id, which will be used to sign onto the Azure portal later.

6. Click You're ready to go, which will take you to the following screen:

   

7. Click on the Admin app icon, which will open the Office365 admin center page in your browser. It will look like this:

   

   If you'd like to see the welcome tour click Next, or simply close the dialog box.

Stay on this page until the next exercise.

---

Exercise 2: Set up Azure trial subscription

Next, we want to set up an Azure subscription. Go to azure.microsoft.com/en-us/free and click Free trial.

If the free trial option is not available login to portal.office.com and click Cost Management + Billing in the menu on the left. This will open the Cost Management + Billing blade. From the blade's menu select Subscriptions and click on New subscription at the top of the blade:

From the list select the Developer support option to create a Azure trial:

BEGIN Steps for Azure Pass redemption - Follow this step if you are using an Azure Pass. If you are not using an Azure Pass, please skip ahead to END Steps for Azure Pass redemption

1. Navigate to www.microsoftazurepass.com and sign in. Make sure to clean your browser cache and use a private window! The sign in screen must display the company icon shown on the left side:

   

2. Enter the code that is provided by your facilitator into the text box, then click Claim Promo Code.

   

3. Click Activate.

   

END Steps for Azure Pass redemption

1. After clicking on the Azure Subscription link you will be taken to the page for creating a new trial subscription:

   

2. Enter the requested information and click Next.

3. Enter the information about you, and verify your identity by phone.

4. Next, you will need to verify via credit card. Your credit card will not be charged unless you remove the spending cap from your subscription. Supported cards must be either a Credit or Debit card, from vendors Visa, Mastercard, American Express, or Discover.

   

5. Finally after the verification process, you'll have to agree to the terms of the trial subscription and click the Sign up button.

   

6. It will take a few moments to set up your Azure subscription.

   

7. When the subscription set up process is complete, click on Get started with your Azure subscription button:

   

You should now be taken to the Azure Portal where you can explore your new Azure Trial Subscription.

---

Exercise 3: Start your VSTS trial subscription

In a future lab we will use Visual Studio Team Services, or "VSTS" for short. In this exercise we will enable a free trial subscription.

1. In your browser, go to www.visualstudio.com/team-services and click on Sign in in the upper right corner.

   

   Complete the sign in process if needed, and you should be taken to a screen that looks like this:

   

   Add your name and email address (if not already populated) and click Continue.

2. On the My Benefits screen, click Use your benefits under the heading Visual Studio Dev Essentials.

   

3. Click the Accept button to access your Visual Studio Dev Essentials benefits.

   

   Click Confirm in the modal dialogue.

   

You have now activated a Visual Studio Team Services Trial Subscription, which will be used in a future lab.

---

Exercise 4: Configure your Azure subscription for DevCamp

1. We have created an Azure Resource Group template that will configure the resources you need in Azure for the DevCamp. To deploy these resources in your Azure subscription, control + click on the blue Deploy to Azure button below (on a MAC, use Apple Key + click):

   👉 👈

2. You should see a new tab open in your browser and open the Azure portal, with a blade that looks like this:

   

3. Name your resource group DevCamp, and choose a location for your deployment.

   Please do not choose the region West India for your deployment. It is missing a resource that is needed for the labs!

4. Check the box that indicates you agree to the terms and conditions, and click the Purchase button.

   The Resource Group template will start deploying, and the portal may pin a tile to the dashboard showing the status:

   

   It will also be visible in the Notifications dropdown:

   

5. This will take approximately 20-30 minutes to complete. Please do not continue on until the template has completed.

   In a later session, we will take a look at Azure Resource Group templates, and how to manage your infrastructure the same way you manage your code. As a short introduction, a template is a JSON file that contains definitions for the resources you want in your resource group. When you apply the resource group template, Azure will apply the template to your Azure resource group, and create the resources you have specified in the template. This makes it easy to maintain the infrastructure definition in the JSON text file.

   In the resource group template we have created for DevCamp, there are several types of resources including Web Apps and a Virtual Machine. Resource Group Templates are usually fairly quick to apply - the reason this one takes so long is that we are creating a Windows Virtual machine and installing all the tools you will need for the DevCamp including Visual Studio, the Java development kit, and other software resources.

6. You will know when the Resource Group finishes provisioning either by the Notification drop-down, or by navigation on the left-hand bar to Resource Groups -> DevCamp and check the Deployments status for Succeeded.

   

   Once the Resource Group creation is done, you can visit the resource group by clicking Resource Groups on the left navigation pane:

   

7. Then click on your Resource group to open it:

   

---

Exercise 5: Use an Azure Virtual Machine for remote development

1. The Azure resource group template will have created a virtual machine that can be used for remote development on Windows. Exercise 5 describes the configuration for the Windows virtual machine, which would be appropriate for any of the languages.

2. In the DevCamp resource group, select the DevCamp DevTest Lab.

   

3. Find the Windows virtual machine in your DevTest lab. The name will start with the prefix windev:

   

4. Select the machine name and open the virtual machine blade then click Connect to connect to the machine using Remote Desktop:

   

   This will download a remote desktop connection file, and when you open it, remote desktop on your local machine will attempt to attach to your virtual machine.

   

   When the windows security dialog pops up, the user name l-admin should be pre-selected. If not click on the More choices link, then choose Use a different account.

   

5. Use the following credentials to log on to the machine:

   User Name = .\l-admin

   Password = Devc@mp2016!

   

   It would be wise to change the password in the virtual machine.

6. When remote desktop is connected, you will see server manager initially. We will want to turn of IE enhanced security, to make accessing the web within the virtual machine easier. First click local server.

   

7. Then click the On next to IE Enhanced Security Configuration.

   

   A dialog box pops up - choose to turn enhanced security off for administrators.

8. We are going to use git to clone the DevCamp github repository to this development machine. Click on the Start menu, and type cmd.

   NOTE: On some high resolution monitors (HIGH DPI), you will notice that the icons and command line windows appear small. If this is an issue, you can download Remote Desktop Connection Manager 2.7.

9. Change directory to the root using cd c:\ .

10. Type git clone https://github.com/AzureCAT-GSI/DevCamp.git:

    

    All of the content for this DevCamp will now be located in c:\DevCamp.

11. Start Visual Studio using the Visual Studio 2015 shortcut.

    Note, there are 2 Visual Studio shortcuts. Make sure you DO NOT use the "start experimental instance of visual studio 2015" shortcut.

    

12. On the sign in screen, click sign in. Use the credentials you used earlier for your Office 365 trial subscription.

    Depending on the version of the Windows image and Visual Studio, your start experience may vary:

    

    or

    

13. Create a VSTS repository. Enter a repository name and click continue:

    

14. Create your first team project, and name it DevCamp:

    

15. If the VSTS dialog does not appear during your setup process use the Team Explorer to open it manually by selecting Get started for free in the Visual Studio Team Services section.

    

16. Enter a repository name, select Git and click Continue:

    

17. After the repository has been created click Clone in Visual Studio:

    

18. In Visual Studio click Clone to confirm the settings.

19. Click close. You are done with the Visual Studio setup.

20. Close the remote desktop connection.

---

Exercise 6: Deploy shared API application

1. The API application has been prepared for you to be available as a communication partner during different exercises and just needs to be deployed once. It will be first used in the second hands on lab.

2. Open a browser and navigate to https://portal.azure.com. Locate the app service named incidentapi... in the resource group blade:

   

3. Click on the app service, which will bring up the app service blade. Click on Browse at the top:

   

   A new browser tab will open.

   If the page looks like the image displayed below, this means the API was automatically deployed from GitHub, and you can skip the rest of this exercise.

   

   If the page looks like the image below, continue with this exercise

   

4. In the Azure portal, select the API Application (noted with the icon).

   

5. On the details blade select Deployment options.

   

6. If the app deployment is connected, click Disconnect on the menu bar.

   

7. Then select Choose source in the blade and select External Repository.

   

8. Paste the following in the Repository URL field https://github.com/AzureCAT-GSI/DevCamp.git.

   

9. Select OK.

---

Exercise 7: Azure Portal walk-through

1. On your local machine or the virtual machine in Azure, open a browser window and go to the main Azure portal page, http://portal.azure.com. Log in with the credentials you supplied in the subscription sign-up exercise. You should see the Azure portal, similar to this:

   

   There is a lot to notice on this screen. At the upper left corner, the icon under the Microsoft Azure banner allows you to shrink and expand the left bar:

   

   Under that, clicking on the + New item will allow you to create new deployments, virtual machines, databases, etc:

   

2. On the left you will see a list of the Azure services that you can use on the left hand side. Notice that this list will scroll up and down to reveal more services, and finally an item that says More Services >:

   

   You can click on any of these and see what items are deployed, and easily create new deployments.

3. At the top of the window you have a search box where you can search for any resources:

   

4. The bell icon is for notifications, and in this screenshot, it indicates that there are two notifications pending:

   

   Clicking on the bell will show you the notifications:

   

   If you click on one of the notifications, you can go to the details blade that matches the content of the notification, e.g. the details blade of the starting virtual machine.

5. The >_ icon opens the Azure Cloud Shell which gives you authenticated shell access to Azure within the browser. It opens at the bottom of the window.

   

6. The gear at the top of the screen lets you set the color palate for the portal, whether or not there will be animations, and other options for the portal itself:

   

7. The "smiley face" button allows you to send feedback to Microsoft:

   

   Clicking on the icon will give you a form to let us know about your experience:

   

8. The Question icon will give you the ability to enter a support case, manage support requests, or get further information on Azure.

   

9. Your login name and company name on the upper left hand corner has two functions:

   

   If you hover the mouse over your name, you'll get information about your login, the directory and subscription:

   

   If you click on your name, you can sign out, change your password, view your permissions, and view your bill:

   

10. Next we will look at the resource group we set up with the template. Click on Resource Groups on the left hand side:

    

11. Click on the resource group that you created:

    

    A new blade will open with the overview of all of the contents of the resource group listed:

    

    You can click on any of the items on the left hand side which will view or manipulate settings for the resource group as a whole. If you click on any of the individual resources in the center, you will get more information on that resource.

12. Azure automatically logs changes to resource group and who made those changes. Clicking Activity log on the left of the blade will allow you to query the log, and clicking on any logged items will give you additional information on that entry:

    

13. Clicking on Automation script will allow you to view, edit or download the resource group template that would create this resource group.

    

14. The Windows VM is managed by an Azure DevTest lab named DevCamp which handles the startup and shutdown of the machine. To change the start up schedule, click on the DevTest Lab icon and select Configuration and policies under the Settings headline.

    

    

15. Select Auto-shutdown.

    

16. Modify the Auto-shutdown schedule based on your time zone.

    

The Azure portal is currently in a re-designing phase during which the Auto-Start option may not be available at all times. Skip the next to steps if it does not show up on the VM's menu.

1. The machine does not automatically turn on. To enable this, in the Policy Settings blade, select Auto-Start.

   

2. Change the schedule based on your time zone.

   

It is particularly useful to create resources in the Azure portal, then save or edit the resource group template. Resource group templates will be explained further in a later lab.

---

Exercise 8: View the resources you created

Going back to the list of resources in the resource group DevCamp, we'll go through the list of each resource, with a description. Feel free to click on the resource and view its detail blade.

Also, our resource group template has added a random string to the end of many of the resources. In this description, we have replaced that string with ...:

• adevcamp... - Storage account for storing artifacts for the DevTest labs.

• DevCamp - This is the DevTest lab that is used to manage the VM images and artifacts.

• DevCamp... - This is the Azure Key Vault that is used to manage secure credentials.

• DevCampVnet - This is an Azure Virtual Network, which will allow components of the resource group to communicate as if they were on the same physical network.

• dotnetapp... - App service for running the .NET application when deployed to the cloud. If you are not using .NET in the labs, you can safely delete this.

• incidentapi... - App service for running the API service that provides a REST API to the web applications.

• incidentappplan... - App Service Plan, which defines how the app services in the resource group will be configured.

• incidentblobstg... - Storage account for storing the uploaded images and the Azure Queue, from the modern-cloud-apps hands on lab.

• incidentcache... - This is the Redis cache that we use from the application to make data access faster. The modern-cloud-apps hands on lab adds support to the application to be able to leverage the cache.

• incidentdb... - This is the CosmosDB database that will hold the JSON incident documents stored by the application.

• incidentdiagstg... - Storage account for storing diagnostics from the services in the resource group.

• javaapp... - App service for running the Java application when deployed to the cloud. If you are not using Java in the labs, you can safely delete this.

• nodejsapp... - App service for running the Node.js application when deployed to the cloud. If you are not using Node.js in the labs, you can safely delete this.

In the second resource group DevCamp-WinDev-..., additional resources were created.

They are all called WinDev-... but are of different types:

• Public IP address - This is a public IP that will allow the Windows development virtual machine to communicate with the Internet (e.g. via Remote Desktop). If you delete the Windows virtual machine, you can safely delete this.

• Virtual machine - This is the Windows server virtual machine that we are using as a development machine for these hands-on-labs. You can delete this machine after the developer-environment lab if you are using an on-premises/local machine for development.

• Network interface - This is a public network interface that will allow the Windows development virtual machine to communicate on the network. If you delete the Windows virtual machine, you can safely delete this.

• Disk - Storage account for storing for VHDs for the machines DevTest labs.

---

Clean Up

🔺 Please refer back to this section after the DevCamp concludes! This is instructional only! Do NOT clean up until the DevCamp is done! 🔺

To clean up a Resource Group, we typically simply delete the Resource Group. However, since we are using an Azure DevTest Lab to manage our Virtual Machine, we have an additional step.

Azure DevTest Labs create a series of Resource Locks that prevent accidental deletion of resources. Locks allow us to safeguard against accidental deletion of critical resources, and to delete the Resource Group we first need to delete the locks.

Open your DevCamp Resource Group, and in the navigation pane select Locks. You should see the 3 locks created by the DevTest Lab. To delete, select the three dots to the right of the Notes column, and select Delete.

After all 3 locks have been deleted you are able to delete the resource group. Navigate to the Overview tab and select Delete. The Resource Group will take several minutes to remove, but when finished all resources will no longer accrue charges in your subscription.

---

Summary

In this hands-on lab, you learned how to:

• Set up an Office365 developer subscription.
• Set up an Azure trial subscription allowing you to complete this course free of charge.
• Configure your Azure subscription for DevCamp.
• Create an Azure Virtual Machine for development where you can carry out the following hands on labs.
• Connect to the Azure Virtual Machine and configure it for development.
• Use the Azure portal to view the resources that you created giving you a first overview of the management of Azure resources.

After completing this module, you can continue on to Module 2: Building modern cloud apps.

View Module 2 instructions for .NET.

---

Copyright 2016 Microsoft Corporation. All rights reserved. Except where otherwise noted, these materials are licensed under the terms of the MIT License. You may use them according to the license as is most appropriate for your project. The terms of this license can be found at https://opensource.org/licenses/MIT.