Skip to content

Latest commit

 

History

History
 
 

05.multi-turn-prompt

This sample demonstrates a the use of multiple prompts with ASP.Net Core 2.

To try this sample

  • Clone the samples repository
git clone https://github.com/Microsoft/botbuilder-samples.git
  • [Optional] Update the appsettings.json file under botbuilder-samples/samples/csharp_dotnetcore/05.multi-turn-prompt with your botFileSecret. For Azure Bot Service bots, you can find the botFileSecret under application settings.

Prerequisites

Visual Studio

  • Navigate to the samples folder (botbuilder-samples/samples/csharp_dotnetcore/05.multi-turn-prompt) and open MultiTurnPromptsBot.csproj in Visual Studio.
  • Hit F5.

Visual Studio Code

  • Open botbuilder-samples/samples/csharp_dotnetcore/05.multi-turn-prompt sample folder.
  • Bring up a terminal, navigate to botbuilder-samples/samples/csharp_dotnetcore/05.multi-turn-prompt folder.
  • Type 'dotnet run'.

Update packages

  • In Visual Studio right click on the solution and select "Restore NuGet Packages". Note: this sample requires Microsoft.Bot.Builder, Microsoft.Bot.Builder.Dialogs and Microsoft.Bot.Builder.Integration.AspNet.Core.

Testing the bot using Bot Framework Emulator

Microsoft 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 from here.

Connect to bot using Bot Framework Emulator V4

  • Launch the Bot Framework Emulator.
  • File -> Open bot and navigate to botbuilder-samples/samples/csharp_dotnetcore/05.multi-turn-prompt folder.
  • Select BotConfiguration.bot file.

Deploy this bot to Azure

You can use the MSBot Bot Builder CLI tool to clone and configure any services this sample depends on.

To install all Bot Builder tools -

Ensure you have Node.js version 8.5 or higher

npm i -g msbot chatdown ludown qnamaker luis-apis botdispatch luisgen

To clone this bot, run

msbot clone services -f deploymentScripts/msbotClone -n <BOT-NAME> -l <Azure-location> --subscriptionId <Azure-subscription-id>

Further reading