Tutorial: Deploy an ASP.

NET app to
Azure with Azure SQL Database
Azure App Service provides a highly scalable, self-patching web hosting service. This
tutorial shows you how to deploy a data-driven ASP.NET app in App Service and
connect it to Azure SQL Database. When you're finished, you have an ASP.NET app
running in Azure and connected to SQL Database.

Run the app

1. Open the dotnet-sqldb-tutorial-master/DotNetAppSqlDb.sln file in Visual

Studio.

2. Type Ctrl+F5 to run the app without debugging. The app is displayed in

your default browser.

3. Select the Create New link and create a couple to-do items.

4. Test the Edit, Details, and Delete links.

The app uses a database context to connect with the database. In this sample, the
database context uses a connection string named MyDbConnection. The connection string
is set in the Web.config file and referenced in the Models/MyDatabaseContext.cs file. The
connection string name is used later in the tutorial to connect the Azure app to an Azure
SQL Database.

Publish ASP.NET application to Azure

1. In the Solution Explorer, right-click your DotNetAppSqlDb project and

select Publish.

2. Select Azure as your target and click Next.

3. Make sure that Azure App Service (Windows) is selected and click Next.

Sign in and add an app

1. In the Publish dialog, click Sign In.

2. Sign in to your Azure subscription. If you're already signed into a Microsoft

account, make sure that account holds your Azure subscription. If the
signed-in Microsoft account doesn't have your Azure subscription, click it to
add the correct account.

3. In the App Service instances pane, click +.

Configure the web app name

You can keep the generated web app name, or change it to another unique name (valid
characters are a-z, 0-9, and -). The web app name is used as part of the default URL for
your app (<app_name>.azurewebsites.net, where <app_name> is your web app name). The
web app name needs to be unique across all apps in Azure.

 Note

Don't select Create yet.

Create a resource group

A resource group is a logical container into which Azure resources, such as web apps,
databases, and storage accounts, are deployed and managed. For example, you can
choose to delete the entire resource group in one simple step later.

1. Next to Resource Group, click New.

2. Name the resource group myResourceGroup.

Create an App Service plan

An App Service plan specifies the location, size, and features of the web server farm that
hosts your app. You can save money when you host multiple apps by configuring the
web apps to share a single App Service plan.

App Service plans define:

 Region (for example: North Europe, East US, or Southeast Asia)

 Instance size (small, medium, or large)
 Scale count (1 to 20 instances)
 SKU (Free, Shared, Basic, Standard, or Premium)

1. Next to Hosting Plan, click New.

2. In the Configure App Service Plan dialog, configure the new App Service

plan with the following settings and click OK:

TABLE 1

Setting Suggested value For more information

App Service Plan myAppServicePlan App Service plans

Location West Europe Azure regions

Size Free Pricing tiers

3.

4. Click Create and wait for the Azure resources to be created.

5. The Publish dialog shows the resources you've configured. Click Finish.

Create a server and database

Before creating a database, you need a logical SQL server. A logical SQL server is a
logical construct that contains a group of databases managed as a group.

1. In the Publish dialog, scroll down to the Service Dependencies section.

Next to SQL Server Database, click Configure.
  Note

Be sure to configure the SQL Database from the Publish page instead of

the Connected Services page.

2. Select Azure SQL Database and click Next.

3. In the Configure Azure SQL Database dialog, click +.

4. Next to Database server, click New.

The server name is used as part of the default URL for your
server, <server_name>.database.windows.net. It must be unique across all
servers in Azure SQL. Change the server name to a value you want.

5. Add an administrator username and password. For password complexity

requirements, see Password Policy.

Remember this username and password. You need them to manage the
server later.

 Important

Even though your password in the connection strings is masked (in Visual
Studio and also in App Service), the fact that it's maintained somewhere
adds to the attack surface of your app. App Service can use managed
service identities to eliminate this risk by removing the need to maintain
secrets in your code or app configuration at all. For more information,
see Next steps.

6. Click OK.

7. In the Azure SQL Database dialog, keep the default generated Database

Name. Select Create and wait for the database resources to be created.
Configure database connection

1. When the wizard finishes creating the database resources, click Next.

2. In the Database connection string Name, type MyDbConnection. This

name must match the connection string that is referenced
in Models/MyDatabaseContext.cs.

3. In Database connection user name and Database connection password,

type the administrator username and password you used in Create a server.

4. Make sure Azure App Settings is selected and click Finish.

 Note

If you see Local user secrets files instead, you must have configured SQL
Database from the Connected Services page instead of the Publish page.

5. Wait for configuration wizard to finish and click Close.

Deploy your ASP.NET app

1. In the Publish tab scroll back up to the top and click Publish. Once your

ASP.NET app is deployed to Azure. Your default browser is launched with
the URL to the deployed app.

2. Add a few to-do items.

Congratulations! Your data-driven ASP.NET application is running live in

Azure App Service.

Access the database locally

Visual Studio lets you explore and manage your new database in Azure easily in the SQL
Server Object Explorer. The new database already opened its firewall to the App
Service app that you created, but to access it from your local computer (such as from
Visual Studio), you must open a firewall for your local machine's public IP address. If
your internet service provider changes your public IP address, you need to reconfigure
the firewall to access the Azure database again.

Create a database connection

1. From the View menu, select SQL Server Object Explorer.

2. At the top of SQL Server Object Explorer, click the Add SQL

Server button.

Configure the database connection

1. In the Connect dialog, expand the Azure node. All your SQL Database

instances in Azure are listed here.

2. Select the database that you created earlier. The connection you created
earlier is automatically filled at the bottom.

3. Type the database administrator password you created earlier and

click Connect.

Allow client connection from your computer

The Create a new firewall rule dialog is opened. By default, a server only allows

connections to its databases from Azure services, such as your Azure app. To connect to
your database from outside of Azure, create a firewall rule at the server level. The
firewall rule allows the public IP address of your local computer.

The dialog is already filled with your computer's public IP address.

1. Make sure that Add my client IP is selected and click OK.

Once Visual Studio finishes creating the firewall setting for your SQL
Database instance, your connection shows up in SQL Server Object
Explorer.
 Here, you can perform the most common database operations, such as run
queries, create views and stored procedures, and more.

2. Expand your connection > Databases > <your database> > Tables. Right-

click on the Todoes table and select View Data.

Update app with Code First Migrations

You can use the familiar tools in Visual Studio to update your database and app in
Azure. In this step, you use Code First Migrations in Entity Framework to make a change
to your database schema and publish it to Azure.

For more information about using Entity Framework Code First Migrations, see Getting
Started with Entity Framework 6 Code First using MVC 5.

Update your data model

Open Models\Todo.cs in the code editor. Add the following property to the ToDo class:

C#Copy
public bool Done { get; set; }
Run Code First Migrations locally

Run a few commands to make updates to your local database.

1. From the Tools menu, click NuGet Package Manager > Package Manager

Console.

2. In the Package Manager Console window, enable Code First Migrations:

PowerShellCopy
Enable-Migrations

3. Add a migration:

PowerShellCopy
Add-Migration AddProperty

4. Update the local database:

 PowerShellCopy
Update-Database

5. Type Ctrl+F5 to run the app. Test the edit, details, and create links.

If the application loads without errors, then Code First Migrations has succeeded.
However, your page still looks the same because your application logic is not using this
new property yet.

Use the new property

Make some changes in your code to use the Done property. For simplicity in this tutorial,
you're only going to change the Index and Create views to see the property in action.

1. Open Controllers\TodosController.cs.

2. Find the Create() method on line 52 and add Done to the list of properties in

the Bind attribute. When you're done, your Create() method signature looks
like the following code:

C#Copy
public ActionResult Create([Bind(Include =
"Description,CreatedDate,Done")] Todo todo)

3. Open Views\Todos\Create.cshtml.

4. In the Razor code, you should see a <div class="form-group"> element that

uses model.Description, and then another <div class="form-group"> element
that uses model.CreatedDate. Immediately following these two elements, add
another <div class="form-group"> element that uses model.Done:

C#Copy
<div class="form-group">
@Html.LabelFor(model => model.Done, htmlAttributes: new { @class =
"control-label col-md-2" })
<div class="col-md-10">
<div class="checkbox">
@Html.EditorFor(model => model.Done)
@Html.ValidationMessageFor(model => model.Done, "", new
{ @class = "text-danger" })
</div>
</div>
</div>
 5. Open Views\Todos\Index.cshtml.

6. Search for the empty <th></th> element. Just above this element, add the
following Razor code:

C#Copy
<th>
@Html.DisplayNameFor(model => model.Done)
</th>

7. Find the <td> element that contains the Html.ActionLink() helper

methods. Above this <td>, add another <td> element with the following
Razor code:

C#Copy
<td>
@Html.DisplayFor(modelItem => item.Done)
</td>

That's all you need to see the changes in the Index and Create views.

8. Type Ctrl+F5 to run the app.

You can now add a to-do item and check Done. Then it should show up in your
homepage as a completed item. Remember that the Edit view doesn't show
the Done field, because you didn't change the Edit view.

Enable Code First Migrations in Azure

Now that your code change works, including database migration, you publish it to your
Azure app and update your SQL Database with Code First Migrations too.

1. Just like before, right-click your project and select Publish.

2. Click More actions > Edit to open the publish settings.

3. In the MyDatabaseContext dropdown, select the database connection for

your Azure SQL Database.
 4. Select Execute Code First Migrations (runs on application start), then
click Save.

Publish your changes

Now that you enabled Code First Migrations in your Azure app, publish your code
changes.

1. In the publish page, click Publish.

2. Try adding to-do items again and select Done, and they should show up in
your homepage as a completed item.

All your existing to-do items are still displayed. When you republish your ASP.NET
application, existing data in your SQL Database is not lost. Also, Code First Migrations
only changes the data schema and leaves your existing data intact.

Stream application logs

You can stream tracing messages directly from your Azure app to Visual Studio.

Open Controllers\TodosController.cs.

Each action starts with a Trace.WriteLine() method. This code is added to show you how
to add trace messages to your Azure app.

Enable log streaming

1. From the View menu, select Cloud Explorer.

2. In Cloud Explorer, expand the Azure subscription that has your app and
expand App Service.

3. Right-click your Azure app and select View Streaming Logs.

 The logs are now streamed into the Output window.

However, you don't see any of the trace messages yet. That's because when
you first select View Streaming Logs, your Azure app sets the trace level
to Error, which only logs error events (with the Trace.TraceError() method).

Change trace levels

1. To change the trace levels to output other trace messages, go back

to Cloud Explorer.

2. Right-click your app again and select Open in Portal.

3. In the portal management page for your app, from the left menu,
select App Service logs.

4. Under Application Logging (File System), select Verbose in Level.

Click Save.