CoreBot

Bot Framework v4 core bot sample.

This bot has been created using Bot Framework, it shows how to:

• Use LUIS to implement core AI capabilities
• Implement a multi-turn conversation using Dialogs
• Handle user interruptions for such things as Help or Cancel
• Prompt for and validate requests for information from the user

Prerequisites

This sample requires prerequisites in order to run.

Overview

This bot uses LUIS, an AI based cognitive service, to implement language understanding.

Install .NET Core CLI

• .NET Core SDK version 2.1

  # determine dotnet version
  dotnet --version

Create a LUIS Application to enable language understanding

LUIS language model setup, training, and application configuration steps can be found here.

To try this sample

• Clone the repository

  git clone https://github.com/microsoft/botbuilder-samples.git

• In a terminal, navigate to samples/csharp_dotnetcore/13.core-bot

• Run the bot from a terminal or from Visual Studio, choose option A or B.

  A) From a terminal

  # run the bot
  dotnet run

  B) Or from Visual Studio

  • Launch Visual Studio
  • File -> Open -> Project/Solution
  • Navigate to samples/csharp_dotnetcore/13.core-bot folder
  • Select CoreBot.csproj file
  • Press F5 to run the project

Testing the bot using Bot Framework Emulator

Bot Framework Emulator is a desktop application that allows bot developers to test and debug their bots on localhost or running remotely through a tunnel.

• Install the Bot Framework Emulator version 4.5.2 or greater from [here][https://github.com/Microsoft/BotFramework-Emulator/releases]

Connect to the bot using Bot Framework Emulator

• Launch Bot Framework Emulator
• File -> Open Bot
• Enter a Bot URL of http://localhost:3978/api/messages

Deploy the bot to Azure

To learn more about deploying a bot to Azure, see Deploy your bot to Azure for a complete list of deployment instructions.

Further reading

• Bot Framework Documentation
• Bot Basics
• Dialogs
• Gathering Input Using Prompts
• Activity processing
• Azure Bot Service Introduction
• Azure Bot Service Documentation
• .NET Core CLI tools
• Azure CLI
• Azure Portal
• Language Understanding using LUIS
• Channels and Bot Connector Service

page_type: sample languages:

• csharp products:
• dotnet description: "Add 150 character max description" urlFragment: "update-this-to-unique-url-stub"

Official Microsoft Sample

Give a short description for your sample here. What does it do and why is it important?

Contents

Outline the file contents of the repository. It helps users navigate the codebase, build configuration and any related assets.

Prerequisites

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.

Setup

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).

Running the sample

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.

Key concepts

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.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.