Skip to content

Commit aaaa0bd

Browse files
v-thprav-thpra
committed
review-1
1 parent 50e25f9 commit aaaa0bd

12 files changed

+28
-28
lines changed

‎learn-pr/azure/develop-test-deploy-azure-functions-with-visual-studio/2-develop-and-test-azure-functions-locally.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
### YamlMime:ModuleUnit
22
uid: learn.develop-test-deploy-azure-functions-with-visual-studio.2-develop-and-test-azure-functions-locally
3-
title: Create and test a simple Azure Function locally with Visual Studio
3+
title: Create and test an Azure Function locally with Visual Studio
44
metadata:
5-
title: Create and test a simple Azure Function locally with Visual Studio
6-
description: Create and test a simple Azure Function locally with Visual Studio.
5+
title: Create and test an Azure Function locally with Visual Studio
6+
description: Create and test an Azure Function locally with Visual Studio.
77
ms.date: 03/01/2023
88
author: ggailey777
99
ms.author: glenga

‎learn-pr/azure/develop-test-deploy-azure-functions-with-visual-studio/3-exercise-develop-and-test-azure-functions-locally.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
### YamlMime:ModuleUnit
22
uid: learn.develop-test-deploy-azure-functions-with-visual-studio.3-exercise-develop-and-test-azure-functions-locally
3-
title: Exercise - Create and test a simple Azure Function locally with Visual Studio
3+
title: Exercise - Create and test an Azure Function locally with Visual Studio
44
metadata:
5-
title: Exercise - Create and test a simple Azure Function locally with Visual Studio
6-
description: Exercise - Create and test a simple Azure Function locally with Visual Studio
5+
title: Exercise - Create and test an Azure Function locally with Visual Studio
6+
description: Exercise - Create and test an Azure Function locally with Visual Studio.
77
ms.date: 03/01/2023
88
author: ggailey777
99
ms.author: glenga

‎learn-pr/azure/develop-test-deploy-azure-functions-with-visual-studio/4-publish-azure-functions.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
### YamlMime:ModuleUnit
22
uid: learn.develop-test-deploy-azure-functions-with-visual-studio.4-publish-azure-functions
3-
title: Publish a simple Azure Function
3+
title: Publish an Azure Function
44
metadata:
5-
title: Publish a simple Azure Function
6-
description: Publish a simple Azure Function
5+
title: Publish an Azure Function
6+
description: Publish an Azure Function
77
ms.date: 03/01/2023
88
author: ggailey777
99
ms.author: glenga

‎learn-pr/azure/develop-test-deploy-azure-functions-with-visual-studio/5-exercise-publish-azure-functions.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
### YamlMime:ModuleUnit
22
uid: learn.develop-test-deploy-azure-functions-with-visual-studio.5-exercise-publish-azure-functions
3-
title: Exercise - Publish a simple Azure Function
3+
title: Exercise - Publish an Azure Function
44
metadata:
5-
title: Exercise - Publish a simple Azure Function
6-
description: Exercise - Publish a simple Azure Function
5+
title: Exercise - Publish an Azure Function
6+
description: Exercise - Publish an Azure Function
77
ms.date: 03/01/2023
88
author: ggailey777
99
ms.author: glenga

‎learn-pr/azure/develop-test-deploy-azure-functions-with-visual-studio/includes/1-introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,4 +24,4 @@ In this module, you will:
2424
- Experience developing solutions in Visual Studio or a similar integrated development environment
2525

2626
> [!IMPORTANT]
27-
> The exercises in this module require a local installation of Visual Studio 2022 (hereafter referred to as Visual Studio) in a Windows environment.
27+
> The exercises in this module require a local installation of Visual Studio 2022 in a Windows environment.

‎learn-pr/azure/develop-test-deploy-azure-functions-with-visual-studio/includes/2-develop-and-test-azure-functions-locally.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Users can write, debug, and deploy an Azure Function from within the Azure portal. However, writing functions directly in a production, staging, or test environment might not be suitable. For example, writing automated unit tests for Azure Functions, or using on-demand deployment of Azure Functions to Function Apps in Azure. Usually, developers prefer to use a code editor and development tools rather than the environment provided by the Azure portal. Visual Studio enables you to develop and manage Azure Functions code using other code and services in a single project.
1+
Users can write, debug, and deploy an Azure Function from within the Azure portal. However, writing functions directly in a production, staging, or test environment might not be suitable. For example, writing automated unit tests for Azure Functions, or using on-demand deployment of Azure Functions to Function Apps in Azure. Usually, developers prefer to use a code editor and development tools rather than the environment provided by the Azure portal. Visual Studio enables you to develop and manage Azure Functions code by using other code and services in a single project.
22

33
In the online luxury watch scenario, developers are already familiar with Visual Studio 2022. So, you decide to use Visual Studio as the primary development environment for creating Azure Functions. Additionally, Visual Studio provides an excellent environment for testing your functions locally before deploying them to Azure.
44

@@ -36,7 +36,7 @@ A function app hosts one or more functions. It provides the environment and runt
3636
A function is triggered by an event rather than being called directly from an app. You specify the type of event that triggers each function in your Azure Function App. The events available include:
3737

3838
- **Blob trigger**. This type of function runs when a file is uploaded or modified in Azure Blob storage.
39-
- **Event Hub trigger**. An Event Hubs trigger runs the function when an event hub receives a message.
39+
- **Event Hub trigger**. This trigger runs the function when an event hub receives a message.
4040
- **Azure Cosmos DB trigger**. This trigger runs when a document is added to, or modified in an Azure Cosmos DB database. You can use this trigger to integrate Azure Cosmos DB with other services. For example, if a document representing a customer's order is added to a database, you could use a trigger to send a copy of the order to a queue for processing.
4141
- **Http trigger**. An HTTP trigger runs the function when an HTTP request occurs in a web app. You can also use this trigger to respond to webhooks. A webhook is a callback that occurs when an item hosted by a website is modified. For example, you can create a function triggered by a webhook from a GitHub repository when an item in the repository changes.
4242
- **Queue trigger**. This trigger starts the function when a new item is added to an Azure Storage Queue.
@@ -109,7 +109,7 @@ public static class Function2
109109
}
110110
```
111111

112-
In all cases, a function is passed an *ILogger* parameter. The function can use this parameter to write log messages, which the function app writes to storage for later analysis.
112+
In all cases, a function is passed an `ILogger` parameter. The function can use this parameter to write log messages, which the function app writes to storage for later analysis.
113113

114114
A function also contains metadata that specifies the type of the trigger, security requirements, and any other specific information requirements. You can modify metadata using the *HttpTrigger*, *BlobTrigger*, or other trigger attributes, as shown in the examples. The *FunctionName* attribute that precedes a function is an identifier for the function used by the Function App. This name doesn't have to be the same as the name of the function, but it's good practice to keep them synchronized to avoid confusion.
115115

‎learn-pr/azure/develop-test-deploy-azure-functions-with-visual-studio/includes/3-exercise-develop-and-test-azure-functions-locally.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ In the luxury watch online website scenario, there's a requirement for a functio
55
In this exercise, you implement and test a version of this function locally using Visual Studio.
66

77
> [!NOTE]
8-
> Before starting this exercise, make sure you have VS 2022 installed, along with the Web & Cloud workload extensions **ASP.NET and web development** and **Azure development**.
8+
> Before starting this exercise, make sure you have Visual Studio 2022 installed, along with the Web & Cloud workload extensions **ASP.NET and web development** and **Azure development**.
99
1010
## Create an Azure Function App
1111

‎learn-pr/azure/develop-test-deploy-azure-functions-with-visual-studio/includes/4-publish-azure-functions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Deployment from Visual Studio is a great feature for developers. It allows them
1414

1515
## Continuous deployment
1616

17-
Azure Functions makes it easy to deploy your function app using App Service continuous integration. Azure Functions integrates with numerous deployment sources, which support a workflow where function code updates triggers deployment to Azure.
17+
Azure Functions makes it easy to deploy your function app using App Service continuous integration. Azure Functions integrates with numerous deployment sources, which support a workflow where function code updates trigger deployment to Azure.
1818

1919
Continuous deployment is a great option for projects where multiple and frequent contributions are being integrated. It also lets you maintain source control on your functions code. The following deployment sources are currently supported:
2020

‎learn-pr/azure/develop-test-deploy-azure-functions-with-visual-studio/includes/5-exercise-publish-azure-functions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Here, you use the Azure portal to create an Azure Function App. Then, you deploy
2222

2323
The **Create Function App** pane appears.
2424

25-
1. Select **Consumptio** as the hosting plan. Then on the **Basics** tab, enter the following values for each setting.
25+
1. Select **Consumption** as the hosting plan. Then on the **Basics** tab, enter the following values for each setting.
2626

2727
> [!NOTE]
2828
> Your function app must have a name unique to Azure. We suggest using something like **\<*your initials*\>watchfunctions**. Use this name wherever you see *\<your-function-app-name\>* in the remainder of the exercise.
@@ -98,7 +98,7 @@ Here, you use the Azure portal to create an Azure Function App. Then, you deploy
9898
:::image type="content" source="../media/5-functions-app.png" alt-text="Screenshot of the Azure portal Function App pane showing the 'Function1' and 'WatchInfo' functions." loc-scope="other"::: <!-- no-loc -->
9999

100100
> [!NOTE]
101-
> The functions are marked as *Read Only*. You cannot modify their settings or configuration from the Azure portal because you published them from Visual Studio. If you need to update either of these functions, make the changes in Visual Studio and publish them again.
101+
> The functions are marked as *Read Only*. You can't modify their settings or configuration from the Azure portal because you published them from Visual Studio. If you need to update either of these functions, make the changes in Visual Studio and publish them again.
102102
103103
1. In the **Function App** pane, select the **URL** (highlighted in the previous image). A browser window opens, and confirms that the function app is up and running.
104104

‎learn-pr/azure/develop-test-deploy-azure-functions-with-visual-studio/includes/6-unit-test-azure-functions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ The first step is to create a project that contains your unit tests, and add it
1616

1717
:::image type="content" source="../media/6-add-xunit-project.png" alt-text="Screenshot of the Add New Project window. The xUnit Test Project template is selected." loc-scope="vs":::
1818

19-
1. The **Configure your new project** window appears. In the **Project name** field, enter *WatchFunctionsTests*. Aside the **Location** field, select the browse icon, and then select the **WatchPortalFunction** folder.
19+
1. The **Configure your new project** window appears. In the **Project name** field, enter *WatchFunctionsTests*. Select the browse icon next to the **Location** field, and then select the **WatchPortalFunction** folder.
2020

2121
1. Select **Next**. The **Additional information** window appears.
2222

@@ -31,7 +31,7 @@ The first step is to create a project that contains your unit tests, and add it
3131
:::image type="content" source="../media/6-nuget-install-aspnet-mvc.png" alt-text="Screenshot of the NuGet Package Manager window. The user is installing the Microsoft.AspNetCore.Mvc package." loc-scope="vs":::
3232

3333
> [!NOTE]
34-
> The test project will create a mock HTTP environment. The classes required for doing this are in the **Microsoft.AspNetCore.Mvc** package.
34+
> The test project creates a mock HTTP environment. The classes required for doing so are in the **Microsoft.AspNetCore.Mvc** package.
3535
3636
1. Wait while the package is installed. If the **Preview Changes** message box appears, select **OK**. In the **License Acceptance** message box, select **I Accept**.
3737

0 commit comments

Comments
 (0)