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
Copy file name to clipboardExpand all lines: ej2-asp-core-mvc/chat-ui/EJ2_ASP.NETCORE/bot-integrations/integration-with-bot-framework.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ documentation: ug
10
10
11
11
# Microsoft Bot Framework With ASP.NET Core Chat UI component
12
12
13
-
The Syncfusion ASP.NET Core Chat UI supports integration with a Microsoft Bot Framework bot hosted on Azure, enabling a custom chat interface for seamless user interaction. The process involves setting up a secure backend token server, configuring the bot in Azure, and integrating the Syncfusion Chat UI in an ASP.NET Core application.
13
+
The Syncfusion ASP.NET MVC Chat UI supports integration with a [Microsoft Bot Framework](https://learn.microsoft.com/en-us/azure/bot-service/bot-builder-basics?view=azure-bot-service-4.0) bot hosted on Azure, enabling a custom chat interface for seamless user interaction. The process involves setting up a secure backend token server, configuring the bot in Azure, and integrating the Syncfusion Chat UI in an ASP.NET Core application.
14
14
15
15
## Getting Started With the ChatUI Component
16
16
@@ -19,7 +19,7 @@ Before integrating Microsoft Bot Framework, ensure that the Syncfusion Chat UI c
19
19
20
20
## Prerequisites
21
21
22
-
*`Microsoft Azure Account`: Required to create and host the bot.
22
+
*[Microsoft Azure Account](https://portal.azure.com/#home): Required to create and host the bot.
23
23
*`.NET SDK`: Version 6.0 or higher for ASP.NET Core.
24
24
*`Syncfusion EJ2 ASP.NET Core`: Install Syncfusion.EJ2.AspNet.Core in your project.
25
25
*`Deployed Azure Bot`: A bot should be created and published using the Bot Framework, accessible via an Azure App Service. Refer to [Microsoft's Bot Creation Guide](https://learn.microsoft.com/en-us/azure/bot-service/).
1. In the [Azure Portal](https://portal.azure.com/#home), navigate to your bot resource.
48
48
49
-
2. Enable the Direct Line channel:
49
+
2. Enable the direct line channel:
50
50
* Go to `Channels` > `Direct Line` > `Default-Site`.
51
51
* Copy one of the displayed secret keys.
52
52
53
-
3. Verify the Messaging endpoint in the Configuration section (e.g., https://your-bot-service.azurewebsites.net/api/messages).
53
+
3. Verify the messaging endpoint in the configuration section (e.g., https://your-bot-service.azurewebsites.net/api/messages).
54
54
55
55
> `Security Note`: Never expose the Direct Line secret key in frontend code. Use a backend token server to handle it securely.
56
56
57
57
## Set Up Token Server
58
58
59
-
Create a controller in your ASP.NET Core project to handle Direct Line token generation. Add `Controllers/TokenController.cs`:
59
+
Create a controller in your ASP.NET Core project to handle direct line token generation. Add `Controllers/TokenController.cs`:
60
60
61
61
{% tabs %}
62
62
{% highlight cs tabtitle="TokenController.cs" %}
@@ -262,7 +262,7 @@ dotnet run
262
262
263
263
```
264
264
265
-
Open your app in the browser (e.g., `http://localhost:5000`) to interact with your Microsoft Bot Framework chatbot.
265
+
Open your app in the browser Hosted link to interact with your Microsoft Bot Framework chatbot.
266
266
267
267
## Troubleshooting
268
268
@@ -272,4 +272,4 @@ Open your app in the browser (e.g., `http://localhost:5000`) to interact with yo
272
272
- Test the bot in the Azure Portal using the `Test in Web Chat` feature to ensure it's running correctly.
273
273
- Check the bot's `Messaging endpoint` in the Configuration section and ensure it is correct and accessible.
274
274
*`Connection Fails on Load`: Verify the token controller is running and accessible. Check the browser console for network errors.
275
-
*`Token Expiration`: Direct Line tokens are short-lived. The Direct Line client typically handles token refresh, but if issues persist, restart the Direct Line connection.
275
+
*`Token Expiration`: direct line tokens are short-lived. The direct line client typically handles token refresh, but if issues persist, restart the direct line connection.
0 commit comments