You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3. Extract the contents of the downloaded zip file to a local folder.
33
34
4. In Explorer, find the Visual Studio Solution (.sln) file for your bot, and double-click it.
34
35
4. In Visual Studio, click **View**, and click **Solution Explorer**.
@@ -62,6 +63,7 @@ This section describes how to enable continuous deployment for a bot that you cr
62
63
Follow these steps if you want to use a source control service *other than* Visual Studio Online or Github. Visual Studio Online and Github will pull the source code for your bot from Azure, so users of those two services can skip these steps.
63
64
64
65
3. For a bot on an App Service plan, find your bot page on Azure, click the **BUILD** tab, find the **Download source code** section, and click **Download zip file**.
The code you downloaded uses an encrypted [.bot file](./v4sdk/bot-file-basics.md). You'll need to update `botFilePath` and `botFileSecret` entires in the appsettings.json or .env file.
133
134
To do that, go to the Azure portal. Select your bot in the portal, then under **App Service Settings** section, click **Application Settings**. In the **Application Settings** pane, you'll
When downloading your bot, you will be given the option to include the settings (containing the keys and secrets) for your bot in your download, which may be necessary for your bot to work. If you choose **Yes**, the `appsettings.json` or `.env` file will have the keys.
After you have deployed and tested that the Enterprise Bot Template works end-to-end as listed in the instructions [here](bot-builder-enterprise-template-deployment.md),
17
+
After you have deployed and tested that the Enterprise Bot Template works end-to-end as listed in the instructions [here](bot-builder-enterprise-template-getting-started.md),
19
18
you can easily customize your bot based on your scenario and needs. The goal of the template is to provide a solid foundation upon which to build your conversational experience.
20
19
21
20
## Project Structure
@@ -76,56 +75,56 @@ There are two Cognitive Models included with the Enterprise Template by default,
76
75
To update an existing LUIS model for the Enterprise Template, perform these steps:
77
76
1. Make your changes to the LUIS Model in the [LUIS Portal](http://luis.ai) or using the [LuDown](https://github.com/Microsoft/botbuilder-tools/tree/master/packages/Ludown) and [Luis](https://github.com/Microsoft/botbuilder-tools/tree/master/packages/LUIS) CLI tools.
78
77
2. Run the following command to update your Dispatch model to reflect your changes (ensures proper message routing):
3. Run the following command from your project root for each updated model to update their associated LuisGen classes:
83
-
```shell
82
+
```shell
84
83
luis export version --appId [LUIS_APP_ID] --versionId [LUIS_APP_VERSION] --authoringKey [YOUR_LUIS_AUTHORING_KEY] | luisgen --cs [CS_FILE_NAME] -o "\Dialogs\Shared\Resources"
85
-
```
84
+
```
86
85
87
86
### Updating an existing QnA Maker knowledge base
88
87
To update an existing QnA Maker knowledge base, perform the following steps:
89
88
1. Make changes to your QnA Maker knowledge base via the [LuDown](https://github.com/Microsoft/botbuilder-tools/tree/master/packages/Ludown) and [QnA Maker](https://github.com/Microsoft/botbuilder-tools/tree/master/packages/QnAMaker) CLI tools or the [QnA Maker Portal](https://qnamaker.ai).
90
89
2. Run the following command to update your Dispatch model to reflect your changes (ensures proper message routing):
In scenarios where you wish to add a new LUIS model to your project you need to update the Bot configuration and Dispatcher to ensure it is aware of the additional model.
98
97
1. Create your LUIS model through LuDown/LUIS CLI tools or through the LUIS portal
99
98
2. Run the following command to connect your new LUIS app to your .bot file:
100
-
```shell
99
+
```shell
101
100
msbot connect luis --appId [LUIS_APP_ID] --authoringKey [LUIS_AUTHORING_KEY] --subscriptionKey [LUIS_SUBSCRIPTION_KEY]
102
-
```
101
+
```
103
102
3. Add this new LUIS model to your Dispatcher through the following command
104
-
```shell
103
+
```shell
105
104
dispatch add -t luis -id LUIS_APP_ID -bot "YOUR_BOT.bot" --secret YOURSECRET
106
-
```
105
+
```
107
106
4. Refresh the dispatch model to reflect the LUIS model changes through the following command
The final piece of Dialog infrastruture is the creation of a State class scoped to your Dialog only. Create a new class and ensure it derives from `DialogState`
199
198
200
199
Once your dialog is complete, your need to add the dialog to your `MainDialog` component using `AddDialog`. To use your new Dialog, call `dc.BeginDialogAsync()` from within your `RouteAsync` method, triggering with the appropriate LUIS intent if desired.
201
-
202
-
## Conversational insights using PowerBI dashboard and Application Insights
203
-
- To get started with getting Conversational insights, continue with [Configure conversational analytics with PowerBI dashboard](bot-builder-enterprise-template-powerbi.md).
0 commit comments