Skip to content

Commit b13d33f

Browse files
Update integration-with-bot-framework.md
1 parent 8d838a7 commit b13d33f

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

ej2-asp-core-mvc/chat-ui/EJ2_ASP.NETCORE/bot-integrations/integration-with-bot-framework.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ documentation: ug
1010

1111
# Microsoft Bot Framework With ASP.NET Core Chat UI component
1212

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.
1414

1515
## Getting Started With the ChatUI Component
1616

@@ -19,7 +19,7 @@ Before integrating Microsoft Bot Framework, ensure that the Syncfusion Chat UI c
1919

2020
## Prerequisites
2121

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.
2323
* `.NET SDK`: Version 6.0 or higher for ASP.NET Core.
2424
* `Syncfusion EJ2 ASP.NET Core`: Install Syncfusion.EJ2.AspNet.Core in your project.
2525
* `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/).
@@ -46,17 +46,17 @@ dotnet add package Syncfusion.EJ2.AspNet.Core
4646

4747
1. In the [Azure Portal](https://portal.azure.com/#home), navigate to your bot resource.
4848

49-
2. Enable the Direct Line channel:
49+
2. Enable the direct line channel:
5050
* Go to `Channels` > `Direct Line` > `Default-Site`.
5151
* Copy one of the displayed secret keys.
5252

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).
5454

5555
> `Security Note`: Never expose the Direct Line secret key in frontend code. Use a backend token server to handle it securely.
5656
5757
## Set Up Token Server
5858

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`:
6060

6161
{% tabs %}
6262
{% highlight cs tabtitle="TokenController.cs" %}
@@ -262,7 +262,7 @@ dotnet run
262262

263263
```
264264

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.
266266

267267
## Troubleshooting
268268

@@ -272,4 +272,4 @@ Open your app in the browser (e.g., `http://localhost:5000`) to interact with yo
272272
- Test the bot in the Azure Portal using the `Test in Web Chat` feature to ensure it's running correctly.
273273
- Check the bot's `Messaging endpoint` in the Configuration section and ensure it is correct and accessible.
274274
* `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

Comments
 (0)