Skip to content

Commit 84bf1c9

Browse files
authored
Update README.md
1 parent 1977ac3 commit 84bf1c9

1 file changed

Lines changed: 21 additions & 41 deletions

File tree

README.md

Lines changed: 21 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -1,53 +1,27 @@
1-
---
2-
page_type: sample
3-
languages:
4-
- csharp
5-
products:
6-
- dotnet
7-
description: "Add 150 character max description"
8-
urlFragment: "update-this-to-unique-url-stub"
9-
---
101

11-
# Official Microsoft Sample
2+
# Power Virtual Agents Samples
123

13-
<!--
14-
Guidelines on README format: https://review.docs.microsoft.com/help/onboard/admin/samples/concepts/readme-template?branch=master
4+
## Overview
155

16-
Guidance on onboarding samples to docs.microsoft.com/samples: https://review.docs.microsoft.com/help/onboard/admin/samples/process/onboarding?branch=master
6+
This branch contains samples for connecting your Power Virtual Agents bot to a custom app or to existing [Azure Bot Service channels](/azure/bot-service/bot-service-manage-channels?view=azure-bot-service-4.0).
177

18-
Taxonomies for products and languages: https://review.docs.microsoft.com/new-hope/information-architecture/metadata/taxonomies?branch=master
19-
-->
8+
## Samples list
209

21-
Give a short description for your sample here. What does it do and why is it important?
10+
To use the samples, clone this GitHub repository using Git.
2211

23-
## Contents
12+
```bash
13+
git clone https://github.com/Microsoft/BotBuilder-Samples.git
14+
cd BotBuilder-Samples
15+
```
2416

25-
Outline the file contents of the repository. It helps users navigate the codebase, build configuration and any related assets.
17+
| Sample Name | Description | .NET CORE |
18+
|-----------------------|--------------------------------------------------------------------------------|-------------|
19+
|1.BotConnectorApp | Demonstrates how to connect your bot to a custom app for example mobile-device app | [View][cs#1]|
20+
|2.RelayBotSample | Demonstrates how to connect your bot to existing Azure Bot Service channels | [View][cs#2] |
2621

27-
| File/folder | Description |
28-
|-------------------|--------------------------------------------|
29-
| `src` | Sample source code. |
30-
| `.gitignore` | Define what to ignore at commit time. |
31-
| `CHANGELOG.md` | List of changes to the sample. |
32-
| `CONTRIBUTING.md` | Guidelines for contributing to the sample. |
33-
| `README.md` | This README file. |
34-
| `LICENSE` | The license for the sample. |
22+
[cs#1]:./BotConnectorApp
23+
[cs#2]:./RelayBotSample
3524

36-
## Prerequisites
37-
38-
Outline the required components and tools that a user might need to have on their machine in order to run the sample. This can be anything from frameworks, SDKs, OS versions or IDE releases.
39-
40-
## Setup
41-
42-
Explain how to prepare the sample once the user clones or downloads the repository. The section should outline every step necessary to install dependencies and set up any settings (for example, API keys and output folders).
43-
44-
## Runnning the sample
45-
46-
Outline step-by-step instructions to execute the sample and see its output. Include steps for executing the sample from the IDE, starting specific services in the Azure portal or anything related to the overall launch of the code.
47-
48-
## Key concepts
49-
50-
Provide users with more context on the tools and services used in the sample. Explain some of the code that is being used and how services interact with each other.
5125

5226
## Contributing
5327

@@ -62,3 +36,9 @@ provided by the bot. You will only need to do this once across all repos using o
6236
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
6337
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
6438
contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
39+
40+
41+
## Reporting Security Issues
42+
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at [secure@microsoft.com](mailto:secure@microsoft.com). You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the [MSRC PGP](https://technet.microsoft.com/en-us/security/dn606155) key, can be found in the [Security TechCenter](https://technet.microsoft.com/en-us/security/default).
43+
44+
Copyright (c) Microsoft Corporation. All rights reserved.

0 commit comments

Comments
 (0)