-
Notifications
You must be signed in to change notification settings - Fork 528
[C#][Skills] HTTP transport is not enable in the skills #2377
Comments
Thanks - I've dropped you a mail. WebSockets/Streaming extensions (via /api/skill/messages) is the only supported protocol. i.e. not HTTP. We can discuss later :) |
Hi, |
@darrenj could you please help us here. |
@Kumar3010 Apologies, we didn't notice this comment on a development work-item so didn't fall into our customer tracking. As per this item we have only just recently received the WebSocket streaming extension library for javascript and are integrating it to unblock this scenario (e.g. expose a JS skill) enabling callers to invoke. This is why your typescript skill can't be invoked from a C# Bot (C# skill would be fine) We are working on the changes and the above work item is the one to get updates, we'll hopefully have a daily build that can be used to track updates. |
Tracked by #2489. Please customize notifications to get updates. |
What project is affected?
Skills (we used the Sample Skill specifically)
What language is this in?
C#
What happens?
During the communication between a
Virtual Assistant
inTypeScript
and aSkill
inC#
, we noticed a 404 HTTP error initiating the Skill dialog.Also, we reviewed that in the SkillController is missing a POST endpoint for
api/skill/messages
, so the communication via HTTP transport won't be successful because thebotbuilder-skills
library will prepare a request using the POST method.What are the steps to reproduce this issue?
Using the Sample Assistant in TypeScript and the Sample Skill in C#
Botskills CLI Tool
, connect the VA to the Skillrun sample dialog
utterance to initiate the Sample Skill dialogWhat were you expecting to happen?
The Sample Skill in C# receives the intent correctly and starts the corresponding dialog.
Can you share any logs, error output, etc.?
Any screenshots or additional context?
There is a GET endpoint for api/skill/messages in the
SkillController
which is handled with theWebSocket
functionality.The text was updated successfully, but these errors were encountered: