Give a clear and concise description of what the bug is.
The instructions say
"There are two locations that need to be updated in the code to resolve the LUIS service. In the following files: MainDialog.cs EnterpriseDialog.cs The following line needs to be updated in both files: var luisService = _services.LuisServices[_General]; The must be replaced with the provided in step 4 above."
but (1) this line doesn't exist in either file, and (2) replacing the closest line to it results in a "null", it's not actually hitting the service for some reason
Is there a known fix for this?
Thanks!
Anna
Steps to reproduce the behavior:
Give a clear and concise description of what you expected to happen.
If applicable, add screenshots to help explain your problem.
Add any other context about the problem here.
[bug]
Hi Anna, can you point me to where you saw these instructions? They are out of date and you no longer need to modify this code for the enterprise template to work. I will update the docs accordingly.
You do need to modify the code, at least as of this morning, to update the within the two dialogs the "name" of the luis services. for QnA, you no longer have to because it's default is FAQ
It's not in the docs but it is in the readme which you referenced
It looks like the code in the repo is out of date with the published Visual Studio Marketplace template. We've moved to https://github.com/Microsoft/AI for the latest builds. Would you mind trying to install and build from the template here and let me know if you have the same issues?
Maybe this will help. I'm pulling straight from the samples repo - could that be an issue? These are the steps I'm following (preparing an integration course and this will be part of setup, using the template as a base):
In this lab, we'll walk through how to get a base Enterprise Bot downloaded and deployed with the initial services, including Dispatch, LUIS, QnA Maker, Application Insights, Cosmos DB, Azure Web App Bot, and Azure Storage.
Step 1.3.1: Clone the samples repository
In the future, you may just want to use the VSIX template you downloaded in the previous lab (and now you know how). However, for this solution, the sample is still being updated, and, for now, we want to make sure we're using the most up-to-date template.
In the Cortana search bar, type "git bash" and select "Git Bash Desktop App", or type "cmd" and select "Command Prompt". Next, type cd c: then enter, and git clone https://github.com/Microsoft/BotBuilder-Samples.git then enter. This copies down all of the files from the GitHub site to C:\BotBuilder-Samples.
Step 1.3.2: Create a base solution
Open File Explorer and create a new folder on your desktop called "CSAgent". Next, navigate to "C:\BotBuilder-Samples\samples\csharp_dotnetcore\52.enterprise-bot". Use CTRL+A to select all the files, then CTRL+C to copy them. Navigate to the folder you just created on your Desktop, and use CTRL+V to paste the files into your "CSAgent" folder. Finally, double-click on the "EnterpriseBot" project file (of type "Visual C# Project File") to open it in Visual Studio 2017.
Step 1.3.3: Build the solution
In the solution explorer, right click on the solution and select "Rebuild Solution".
Step 1.3.4: Deploy the related services
This step has multiple steps.
npm install -g chatdown msbot ludown luis-apis qnamaker botdispatch luisgenConnect-AzureRmAccountcd C:\Users\_your-username_\AppData\Roaming\npm to move to the project directory.msbot clone services --name "CSAgent" --luisAuthoringKey "<YOUR AUTHORING KEY>" --folder "C:\Users\<YOUR-USERNAME>\Desktop\CSAgent\DeploymentScripts\msbotClone" --location "westus" --verbose
Note: By default, your Luis Applications will be deployed to your free starter endpoint. An Azure LUIS service will be deployed along with your bot but you must manually add and publish to it from the luis.ai portal and update your key in the .bot file.
y then Enter when prompted to create the resources. And enter the device code in the browser when prompted. This will take several minutes, so be patient, but observe all the things that are being created for you! Want to review line-by-line with us? Step 1.3.5: Updating the base solution
appsettings.json, fill in your botFileSecret with the bot secret you collected in the previous step. Save the file. C:\Users\_your-username_\AppData\Roaming\npm, copy the BOT File, and paste it into the root of your project (should be in a location similar to C:\Users\_your-username_\Desktop\CSAgent)._services.LuisServices) with the value for "name" (make sure it's placed within quotes)._services.QnAServices) with the value for "name" (make sure it's placed within quotes).appsettings.json, replace the "botFilePath" value with the name of your ".bot" file (and including ".bot" in the name). Save all files. Step 1.3.6: Publishing the base solution
As clarification, I've been writing and tweaking these steps as I run into issues. The VSIX template (which I think is what you linked to when you said "here") is out of date isn't it?
I guess my question is - is the most updated version the GitHub samples repo or VSIX template in marketplace?
The VSIX is actually the most up to date because the code is being managed in a separate repo from this one.
Also, the most up to date documentation is on the public docs site here: https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-enterprise-template-deployment?view=azure-bot-service-4.0,
OK that is good to know. I'll start over from the VSIX template and report on any errors I come across. Bugs/comments for VSIX go https://github.com/Microsoft/AI/tree/master/templates/Enterprise-Template and bugs/comments for instructions go https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-enterprise-template-deployment?view=azure-bot-service-4.0 . Correct?
Please submit all bugs and issues to https://github.com/Microsoft/AI/issues. We can update the public docs based on your feedback there!
Will do. thanks
Thanks for your patience!
Moving conversation to AI repo.