Merge pull request #49372 from lootle1/MR73

Stacyrch140 · web-flow · commit e0689a080905 · 2025-03-12T11:08:15.000-04:00
Technical Review 1016254: Publish a Blazor WebAssembly app and .NET A…
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/1-introduction.yml b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/1-introduction.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Introduction
   description: Publish an Azure Static Web App
-  ms.date: 11/14/2023
+  ms.date: 03/04/2025
   author: aaronpowell
   ms.author: aapowell
   ms.manager: markl
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/10-exercise-action.yml b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/10-exercise-action.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Publish the API with GitHub Actions
   description: Exercise - Publish the API with GitHub Actions
-  ms.date: 11/14/2023
+  ms.date: 03/04/2025
   author: aaronpowell
   ms.author: aapowell
   ms.manager: markl
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/11-knowledge-check.yml b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/11-knowledge-check.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Knowledge check
   description: Multiple-choice questions
-  ms.date: 11/14/2023
+  ms.date: 03/04/2025
   author: aaronpowell
   ms.author: aapowell
   ms.manager: markl
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/12-summary.yml b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/12-summary.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Summary
   description: Summary of the app
-  ms.date: 11/14/2023
+  ms.date: 03/04/2025
   author: aaronpowell
   ms.author: aapowell
   ms.manager: markl
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/2-exercise-get-started.yml b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/2-exercise-get-started.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Get started
   description: Exercise - Get started
-  ms.date: 11/14/2023
+  ms.date: 03/04/2025
   author: aaronpowell
   ms.author: aapowell
   ms.manager: markl
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/3-static-web-apps.yml b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/3-static-web-apps.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Plan your Azure Static Web App
   description: Plan your Azure Static Web App
-  ms.date: 11/14/2023
+  ms.date: 03/04/2025
   author: aaronpowell
   ms.author: aapowell
   ms.manager: markl
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/4-exercise-static-web-apps.yml b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/4-exercise-static-web-apps.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Create an Azure Static Web App
   description: Exercise - Create an Azure Static Web App
-  ms.date: 11/14/2023
+  ms.date: 03/04/2025
   author: aaronpowell
   ms.author: aapowell
   ms.manager: markl
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/5-fallback-routes.yml b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/5-fallback-routes.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Configure fallback routes
   description: Configure fallback routes
-  ms.date: 11/14/2023
+  ms.date: 03/04/2025
   author: aaronpowell
   ms.author: aapowell
   ms.manager: markl
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/6-exercise-fallback-routes.yml b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/6-exercise-fallback-routes.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Create your fallback routes
   description: Exercise - Create your fallback routes
-  ms.date: 11/14/2023
+  ms.date: 03/04/2025
   author: aaronpowell
   ms.author: aapowell
   ms.manager: markl
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/7-build-api.yml b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/7-build-api.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Build an API with Azure Functions
   description: Build an API with Azure Functions
-  ms.date: 11/14/2023
+  ms.date: 03/04/2025
   author: aaronpowell
   ms.author: aapowell
   ms.manager: markl
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/8-exercise-function-app.yml b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/8-exercise-function-app.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Create an Azure Functions project
   description: Exercise - Create an Azure Functions project
-  ms.date: 11/14/2023
+  ms.date: 03/04/2025
   author: aaronpowell
   ms.author: aapowell
   ms.manager: markl
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/9-action.yml b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/9-action.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Publish the API with GitHub Actions
   description: Publish the API with GitHub Actions
-  ms.date: 11/14/2023
+  ms.date: 03/04/2025
   author: aaronpowell
   ms.author: aapowell
   ms.manager: markl
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/includes/12-summary.md b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/includes/12-summary.md
@@ -2,9 +2,9 @@ You needed to build a shopping list web app that is secure, and offers solid per
 
 Azure Static Web Apps provides these features as a great fit for this scenario:
 
-- Performance and scale: Your web assets are globally distributed, putting them closer to your users to minimize latency. Your business logic runs on Azure Functions that scales automatically to meet demand.
-- Productivity: You get an automated build pipeline with CI/CD.
-- Security: Your web app is secured with an SSL certificate.
+- **Performance and scale:** Your web assets are globally distributed, putting them closer to your users to minimize latency. Your business logic runs on Azure Functions that scales automatically to meet demand.
+- **Productivity:** You get an automated build pipeline with CI/CD.
+- **Security:** Your web app is secured with an SSL certificate.
 
 *Without* Azure Static Web Apps, you would need to:
 
@@ -26,6 +26,6 @@ Here are several resources where you can learn more about Azure Static Web Apps,
 - Learn how to [Publish an API to Azure Static Web Apps](/training/modules/publish-static-web-app-api-preview-url/)
 - Learn how to [Authenticate users with Azure Static Web Apps](/training/modules/publish-static-web-app-authentication/)
 - [Azure Static Web Apps](/azure/static-web-apps)
-- Learn how to [Deploy to Azure Using Azure Functions](/azure/developer/javascript/how-to/with-web-app/azure-function-resource-group-management/deploy-azure-function-with-visual-studio-code)
+- Learn how to [Deploy to Azure Using Azure Functions](/azure/azure-functions/functions-deployment-technologies)
 - [Overview of Blazor](/aspnet/core/blazor/)
 - Use [Angular](https://code.visualstudio.com/docs/nodejs/angular-tutorial), [React](https://code.visualstudio.com/docs/nodejs/reactjs-tutorial), and [Vue](https://code.visualstudio.com/docs/nodejs/vuejs-tutorial) in Visual Studio Code
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/includes/2-exercise-get-started.md b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/includes/2-exercise-get-started.md
@@ -19,7 +19,7 @@ This module makes it easy for you to create a new repository by using a GitHub t
 
 You just created a GitHub repository named **my-static-blazor-app** in your GitHub account. Next, you clone the repo and run the code locally on your computer.
 
-1. In your GitHub repository, select **Code**, and select **Open with Visual Studio** from the menu. This command prompts you to launch Visual Studio and clone the repository to your machine.
+1. In your GitHub repository, select **Code**, and copy the URL under HTTPS. Open Visual Studio and select Clone a Repository. Add the copied URL to the Repository location, add a Path, and select Clone.
    - If you have multiple versions of Visual Studio installed, ensure your app is opened in Visual Studio 2022 or later.
 
 1. Open the solution file, _ShoppingList.sln_.
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/includes/8-exercise-function-app.md b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/includes/8-exercise-function-app.md
@@ -142,7 +142,7 @@ Now, it's time to watch your web app and Azure Functions project work together.
 
 1. In Visual Studio, right-click the **ShoppingList** solution.
 
-1. Select **Set Startup Projects**.
+1. Select **Configure Startup Projects**.
 
 1. Select the **Multiple startup projects** option.
 
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/includes/9-action.md b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/includes/9-action.md
@@ -12,7 +12,7 @@ The GitHub Action is ready to build and publish your web app and API once it det
 
 Sometimes you want to see your changes in a staging site before publishing to the live web site. Azure Static Web Apps lets you see your changes through preproduction environments that each have their own preview URL. You can create a preproduction environment by creating a pull request against the branch that your GitHub Action is watching. Your live web site isn't affected. Instead, a new version of your app is created in its own preproduction environment. If you go back and check your pull request on GitHub, you notice that a link to the preproduction version is posted in the Conversation tab.
 
-The following table shows how Azure Static Web Apps publishes your app to different URLs. Your app publishes to one URL while a pull request to the same branch publishes to another URL. These autogenerated URLs are provided by Azure Static Web Apps for the production app and pull requests. You can optionally assign a custom domain to the production app.
+The following table shows how Azure Static Web Apps publishes your app to different URLs. Your app publishes to one URL, while a pull request to the same branch publishes to another URL. These autogenerated URLs are provided by Azure Static Web Apps for the production app and pull requests. You can optionally assign a custom domain to the production app.
 
 | Source            | Description       | URL                                                    |
 | ----------------- | ----------------- | ------------------------------------------------------ |
diff --git a/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/index.yml b/learn-pr/azure/publish-app-service-static-web-app-api-dotnet/index.yml
@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Publish a Blazor WebAssembly app and .NET API with Azure Static Web Apps
   description: Publish a Blazor WebAssembly app and .NET API with Azure Static Web Apps
-  ms.date: 11/14/2023
+  ms.date: 03/04/2025
   author: aaronpowell
   ms.author: aapowell
   manager: coxford
@@ -19,9 +19,9 @@ title: Publish a Blazor WebAssembly app and .NET API with Azure Static Web Apps
 summary: Automatically deploy and update a Blazor web application and its API from a GitHub repository.
 abstract: |
   In this module, you will:
-    - Clone and run an existing Blazor web app locally
-    - Create an API for the app with Azure Functions
-    - Publish the app and its API to Azure Static Web Apps
+    - Clone and run an existing Blazor web app locally.
+    - Create an API for the app with Azure Functions.
+    - Publish the app and its API to Azure Static Web Apps.
 prerequisites: |
   - Basic knowledge of web app concepts
   - C# .NET experience at a beginner level
