You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Install <ahref="https://www.visualstudio.com/downloads/"target="_blank">Visual Studio 2022</a> with the **ASP.NET and web development**workload.
33
+
Install <ahref="https://www.visualstudio.com/downloads/"target="_blank">Visual Studio 2022</a> with the **ASP.NET and web development**and **Azure development** workloads.
35
34
36
35
If you've installed Visual Studio already, add the workloads in Visual Studio by clicking **Tools** > **Get Tools and Features**.
37
36
@@ -172,7 +171,7 @@ Before creating a database, you need a [logical SQL server](../azure-sql/databas
172
171
173
172
#### Deploy your ASP.NET app
174
173
175
-
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.
174
+
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.
176
175
177
176
1. Add a few to-do items.
178
177
@@ -182,7 +181,7 @@ Before creating a database, you need a [logical SQL server](../azure-sql/databas
182
181
183
182
## Access the database locally
184
183
185
-
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.
184
+
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.
186
185
187
186
#### Create a database connection
188
187
@@ -350,11 +349,9 @@ Each action starts with a `Trace.WriteLine()` method. This code is added to show
350
349
351
350
#### Enable log streaming
352
351
353
-
1. From the **View** menu, select **Cloud Explorer**.
352
+
1. In the publish page, scroll down to the **Hosting** section.
354
353
355
-
1. In **Cloud Explorer**, expand the Azure subscription that has your app and expand **App Service**.
356
-
357
-
1. Right-click your Azure app and select **View Streaming Logs**.
354
+
1. At the right-hand corner, click **...** > **View Streaming Logs**.
@@ -366,16 +363,14 @@ Each action starts with a `Trace.WriteLine()` method. This code is added to show
366
363
367
364
#### Change trace levels
368
365
369
-
1. To change the trace levels to output other trace messages, go back to **Cloud Explorer**.
366
+
1. To change the trace levels to output other trace messages, go back to the publish page.
370
367
371
-
1. Right-click your app again and select **Open in Portal**.
368
+
1. In the **Hosting** section, click **...** > **Open in Azure portal**.
372
369
373
370
1. In the portal management page for your app, from the left menu, select **App Service logs**.
374
371
375
372
1. Under **Application Logging (File System)**, select **Verbose** in **Level**. Click **Save**.
376
373
377
-

378
-
379
374
> [!TIP]
380
375
> You can experiment with different trace levels to see what types of messages are displayed for each level. For example, the **Information** level includes all logs created by `Trace.TraceInformation()`, `Trace.TraceWarning()`, and `Trace.TraceError()`, but not logs created by `Trace.WriteLine()`.
381
376
@@ -394,22 +389,6 @@ To stop the log-streaming service, click the **Stop monitoring** button in the *
Go to the [Azure portal](https://portal.azure.com) to manage the web app. Search for and select **App Services**.
400
-
401
-

402
-
403
-
Select the name of your Azure app.
404
-
405
-

406
-
407
-
You have landed in your app's page.
408
-
409
-
By default, the portal shows the **Overview** page. This page gives you a view of how your app is doing. Here, you can also perform basic management tasks like browse, stop, start, restart, and delete. The tabs on the left side of the page show the different configuration pages you can open.
410
-
411
-

412
-
413
392
[!INCLUDE [Clean up section](../../includes/clean-up-section-portal-web-app.md)]
414
393
415
394
## Next steps
@@ -423,12 +402,11 @@ In this tutorial, you learned how to:
423
402
> * Deploy the app to Azure
424
403
> * Update the data model and redeploy the app
425
404
> * Stream logs from Azure to your terminal
426
-
> * Manage the app in the Azure portal
427
405
428
406
Advance to the next tutorial to learn how to easily improve the security of your connection Azure SQL Database.
429
407
430
408
> [!div class="nextstepaction"]
431
-
> [Access SQL Database securely using managed identities for Azure resources](tutorial-connect-msi-sql-database.md)
409
+
> [Tutorial: Connect to SQL Database from App Service without secrets using a managed identity](tutorial-connect-msi-sql-database.md)
0 commit comments