Содержание

Create and deploy an ASP.NET web app in Azure App Service
Sign up for Microsoft Azure
Set up the development environment
Create a new project and a web app
Azure Resource Manager templates
Build the Connect(); //2015 Demo web app

Deploy the project to a web app in Azure
Open remote files in Server Explorer
Remote debugging
Monitor and manage the web app in the Azure portal
Azure Key Vault
Other suggested topics to explore

Этот файл содержит неоднозначные символы Юникода, которые могут быть перепутаны с другими в текущей локали. Если это намеренно, можете спокойно проигнорировать это предупреждение. Используйте кнопку Экранировать, чтобы подсветить эти символы.

Create and deploy an ASP.NET web app in Azure App Service

Azure App Service is the only cloud service that integrates everything you need to quickly and easily build web and mobile apps for any platform and any device. Built for developers, App Service is a fully managed platform that has powerful capabilities such as built-in DevOps, continuous integration with Visual Studio Team Services and GitHub, staging and production support, and automatic patching.

This walkthrough shows how to deploy an ASP.NET web application to a web app in Azure App Service by using Visual Studio 2015 or Visual Studio 2013. The walkthrough assumes that you are an ASP.NET developer who has no prior experience with Azure. After you complete the tutorial, you’ll have a web app that’s deployed to Azure from Visual Studio. Samples and tutorials in this article are based on the Connect(); //2015 event demos.

The following illustration shows the completed application:

This article will help you learn the following:

How to prepare your computer for Azure development by installing the Azure SDK for .NET.
How to set up Visual Studio to create a new web app in Azure App Service and an ASP.NET MVC 5 web project.
How to compose the Demo project that is presented in Microsoft Connect(); //2015.
How to deploy a web app project to App Service by using Visual Studio.

How to use the Azure portal to monitor and manage your web app.

You need an Azure account to complete this tutorial. You can:

Open an Azure account for free. You get credits that you can use to try paid Azure services. Even after the credits are used up, you can keep the account and use free Azure services and features, such as the Web Apps feature of Azure App Service.
Activate Visual Studio subscriber benefits. Your Visual Studio subscription gives you credits every month that you can use for paid Azure services.
Get credits every month by joining to Visual Studio Dev Essentials.

If you want to get started with Azure App Service before you sign up for an Azure account, go to Try App Service. There, you can immediately create a short-lived starter web app in App Service without a credit card or commitments.

Set up the development environment

To start, set up your development environment by installing the latest version of the Azure SDK.

Visual Studio 2015▶

Visual Studio 2013▶

If you don't have Visual Studio installed, use the link for Visual Studio 2015, and Visual Studio will be installed along with the SDK.

Create a new project and a web app

Your first step is to create a web project in Visual Studio and a web app in Azure App Service. When that's done, you’ll deploy the project to the web app to make it available on the Internet.

The diagram below illustrates what you're doing in the create and deploy steps.

Open Visual Studio 2015 or Visual Studio 2013.
On the File menu, click New > Project.
In the New Project dialog box, click C# > Web > ASP.NET Web Application.
Choose a good name for the project, for example, HealthDemo.WebApp.
You can deactivate or activate Application Insights if you want your application to be monitored in terms of availability and performance by using Azure Application Insights.
Click OK.

{width="6.5in" height="4.510416666666667in"}

In the Select a template window, select ASP.NET 5 Web Application. On the other side, indicate that you want to host the Web App in Azure. Finally, indicate that you don’t want authentication for the application.

{width="6.489583333333333in" height="5.0625in"}

When you select Azure as the host, a new window will automatically open to indicate that the resources that will be created in Azure, which will host all application resources. Fill in the required information and make sure to indicate the type of deployment as Web App.

{width="6.489583333333333in" height="4.864583333333333in"}

Because your web application will have a SQL database in the future, you can add one as a service in the configuration window.

{width="6.489583333333333in" height="4.864583333333333in"}

When you click the OK button, Azure will begin to create the web app in Azure. After it is deployed, you can see all the information in the Azure portal and in Server Explorer in Visual Studio.

{width="5.614583333333333in" height="1.8645833333333333in"}

{width="6.5in" height="5.041666666666667in"}

Azure Resource Manager templates

You can use an Azure Resource Manager template to provision the services that the applications need. In a single template, you can deploy multiple services along with their dependencies. In that way, you can use the same template to repeatedly deploy your application in different environments during every stage of the application lifecycle.

Azure Quickstart Templates are popular deployments from the community that you can adapt to the needs of the developed application.

Build the Connect(); //2015 Demo web app

In this part of the tutorial, you learn how to develop the ASP.NET 5 Demo shown at Connect(); //2015. In this walkthrough, we show you how to create the skeleton and the structure of the solution. The completed project is in the following location:

Download the Demo solution, which is the result of this walkthrough, to see the structure and organization.

HealthDemo.WebApp.Web

Use the solution that you created in the previous section of this article, and rename the project as HealthDemo.WebApp.Web. The project contains the website that users see, the client-side code of the web application, and the definition of the view.

Make sure that you define this as a startup project and a project that will be deployed in Azure. This project will contain references to other projects including the one that’s included in the solution. You will use the projects to add data, information, and context to the web application.{width="3.96875in" height="5.458333333333333in"}

HealthDemo.WebApp.Model

The following steps help you add an ASP.NET 5 empty project. You should call the project HealthDemo.WebApp.Model. The project contains the model files of the application. Model files are a list of classes that define the data model of the web application that the other projects will use.

{width="3.9375in" height="5.46875in"}

The following files that will be created must be deleted because they aren’t necessary or useful:

File Properties > launchSettings.json.
Node wwwroot.
File Project_Readme.html
File Startup.cs

{width="3.9375in" height="5.46875in"}

Although you could create a Class Library project type , we recommend an ASP.NET project type to contain all references, dependencies, and components that a web project needs.

HealthDemo.WebApp.Data

Create an empty ASP.NET 5 project named HealthDemo.WebApp.Data. Like the previous project, you need to delete the same files and leave an empty project. This project will contain repositories, initial application data, and the infrastructure that is used in the database to store the information about the web application.

{width="3.9895833333333335in" height="5.5in"}

The MyHealthContext file in the project contains the database context as well as two directories:

Infrastructure: Contains the data infrastructure that the web application uses, the data initialization, and the sample images that are used in the application itself.
Repositories: Contains the database repositories that the web application uses. You can find the repositories that access the data in the database and that will be used by the controllers of the application.

HealthDemo.WebApp.API

Finally, create an ASP.NET 5 empty project named HealthDemo.WebApp.API. Delete the files that are indicated in the previous steps so that the final structure of the solution looks like the following illustration:

{width="3.96875in" height="5.5in"}

This project will contain the Web Application API. This is the web service that will provide the data to the web application. The apps have the controllers that have the calls that the application needs to access. The project also uses the repositories that are located in the Data project and the data model that’s in the Model project.

From this point, you have the basic structure of the web application and the availability to deploy it in Azure. Details about the content of each of the projects can be consulted in the repository of the demo shown in Microsoft Connect(); //2015.

Deploy the project to a web app in Azure

To have the web application in an App Service in Azure, just follow a few steps.

With the previous steps, you already generated the Azure resources that can help create more deployments.

In Solution Explorer, right-click the HealthDemo.WebApp.Web project, and then click Publish.

You will see the Publish Web dialog box. The wizard shows you a list of available Publish profiles. If you select Microsoft Azure App Service, you can see a list of available Azure subscriptions and the resource groups that were previously created. Among them is the resource group that you used to deploy the web application that you configured in the previous steps.

After you select the resource group, the page that opens shows the connection information. The default parameters will populate the fields. You can modify the fields if necessary. To check that the connection works correctly, click Validate Connection.

In the Settings page, you can configure the deployment type depending on whether you require a deployment in a production environment or in a debug environment. You can see the connection to the database.

On the last page, Preview, you can determine the changes that affect the Azure environment.

At last, click Publish.

The Output window displays information about the deployment. When it’s finished, a message that everything has been completed successfully is displayed.

You can see the final result in the browser that will open.

Open remote files in Server Explorer

After the web application is deployed in Azure, you can make temporary changes to the remote site. To test and debug in a quick way, you only need to open and modify the files in Server Explorer.

You need to be signed in to Azure by using Server Explorer.
In Server Explorer, expand the node at Azure > App Services > HealthDemo.WebApp.ResourceGroup.
Expand the node Files > approot > src > MyHealth.Web > Views > Home, and open the Index.cshtml file.

{width="3.5104166666666665in" height="6.072916666666667in"}

Replace <li><a asp-controller="Account" asp-action="Login">Private area</a></li> with <li><a asp-controller="Account" asp-action="Login">Secret area</a></li>
Save the file.
Open a browser and open the web app in Azure App Service that you previously created.

{width="6.489583333333333in" height="4.260416666666667in"}

When you see a change in the web, the change is implemented on the website in Azure but not in the local project. So, if you redeploy the project in Azure, these changes will be reversed.

It is also possible to access the configuration of the web application from Visual Studio, start a remote debugging session, and view logs on the application in real time.

Remote debugging

You can place a breakpoint on your solution and debug your application remotely from Azure in Visual Studio*.*

Right-click Publish again and publish debug files/symbols so that you can show remote debugging.

{width="6.5in" height="4.877028652668416in"}

After publishing is finished, on the Debug menu, click Attach to Process, enter the azurewebsites URL along with its port, and select the dnx.exe process.

Finally, from Server Explorer -> App Service, right-click the Application Service node, and attach the debugger. As soon as you run through the breakpoint, the application will stop to be debugged.

{width="5.21875in" height="3.6770833333333335in"}

To learn more about remote debugging, see the Remote Debug ASP.NET Core RC1 on Azure App Service blog post.

Monitor and manage the web app in the Azure portal

You can manage and monitor the services in Azure from the Azure portal. This includes the web application that you just developed.

In a web browser of your choice, go to the Azure portal and sign in with your Azure credentials.
Click Resource groups. Here you can see resource groups for each of the parts that make up the HealthClinic demo that you created in this tutorial: HealthDemo.WebApp.ResourceGroup.

{width="6.5in" height="3.1458333333333335in"}

When you click a resource group, you will see a summary of the resources that are part of the group, as well as the information about the group and its configuration.

{width="6.5in" height="3.1458333333333335in"}

You can click the web application that is contained in the group, HealthDemoWebApp, to view general resource information, statistics, and content about the configuration.

{width="6.5in" height="3.46875in"}

It is possible that statistics are not real or that statistics are not displayed. Explore the application to start to show statistics in the portal.

In the list of configuration types, you can explore different configurations that are available in your application. One is Application settings. From here, you can modify some important aspects of the application.