-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Bot Framework to use new Language Cognitive Service #6413
Comments
I'm having the same issue on NodeJs. #6438 |
Thanks for the feature request. We are currently evaluating how we will integrate with this new service in the Bot SDK. We do not currently have a timeline for this new functionality. |
Is there any update on this? |
There should be support for this in the next update of the SDK. |
Also looking forward to this - we're looking to migrate our chatbot over to the new services whenever this is ready. |
A new message on the QnAMaker site: Starting 1st October, 2022 you won’t be able to create new QnA Maker resources. |
Please provide an update on the timeline @benbrown |
Work on this is progressing, but we have no timeframe yet. |
I have the same doubt, Is there any updates on this @peterswimm ? |
Hey, any update on this? |
@bensaine They added a C# client over in microsoft/botbuilder-dotnet that implements |
Thanks! Do you know if a JS SDK implements it? |
@bensaine With first hand experience, no. But I see they have what appears to be the same client but with a typescript implementation over in the JS library: |
Issue
I am trying to create a new FAQ bot (.NET) using the custom question answering feature. This has recently moved from QnA Maker service to Language Cognitive Service. The Bot Framework does not appear to have a package for interacting with this new service.
Proposed change
A package to integrate with knowledge bases/projects built in Language Studio
Component Impact
All versions of SDK
Tracking Status
Dotnet SDK TODO
Javascript SDK TODO
Python SDK TODO
Java SDK TODO
Samples TODO
Docs TODO
Tools TODO
The text was updated successfully, but these errors were encountered: