This repository has been archived by the owner on Jul 19, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 84
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
2448cdc
commit 9a1ab91
Showing
1 changed file
with
6 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,16 @@ | ||
--- | ||
languages: [] | ||
languages: | ||
- csharp | ||
page_type: sample | ||
products: | ||
- azure | ||
- azure-functions | ||
- azure-app-service | ||
- azure-cosmos-db | ||
- azure-cognitive-services | ||
description: "This sample showcases the new Azure Functions tooling for C# Class Libraries in Visual Studio." | ||
name: "Customer Reviews App with Cognitive Services" | ||
urlFragment: customer-reviews-cognitive-services | ||
--- | ||
|
||
# Sample - Customer Reviews App with Cognitive Services (Azure Functions tools for Visual Studio 2017) | ||
|
@@ -77,4 +81,4 @@ This section highlights how Application Insights custom telemetry can be surface | |
|
||
# Contributing | ||
|
||
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments. | ||
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments. |