BasicBot | basic example of a Discord Bot | Bot library

purge doesn't actually receive a list of messages to delete (though the documentation is phrased as if it does). Instead, it takes a number of keyword arguments that it uses to determine whether or not messages should be deleted. Try

It's pretty similar and the docs you pointed to actually show a successful way to do it. If you'd like to use Dependency Injection, you'd use something like:

The method AddApplicationInsights is included in this package Microsoft.Extensions.Logging.ApplicationInsights.

I setup a .net core 2.1 web app, and configure application insight as well as installing this package Microsoft.Extensions.Logging.ApplicationInsights , version 2.9.1. The logs can be shown both in console and portal.

In code:

Test result - logs in azure portal:

You have to remember that EndDialogAsync will pop just one dialog off the stack, and so if there are any other dialogs still on the stack then the one on top will become the new active dialog and its ResumeDialogAsync will be called, which can potentially send messages.

When the user clicks on the location quick reply in Facebook Messenger, the incoming activity does not have a text property which would cause a 'Value cannot be null' error when calling LUIS. This is currently a known issue in the BotFramework, and the development team is currently working to resolve this problem. In the meantime, check to make sure the incoming activity's text attribute is not null or empty before calling the LUIS recognizer.

This can happen if you are using the Starter Key instead of an actual Subscription Key from an 'endpoint runtime resource in Azure'. More information can be found here: https://docs.microsoft.com/en-us/azure/cognitive-services/luis/luis-how-to-azure-subscription

After creating the LUIS Azure Resource Key, it can be assigned within the LUIS Portal:

More information can be found here: https://docs.microsoft.com/en-us/azure/cognitive-services/luis/get-started-portal-deploy-app#assign-the-resource-key-to-the-luis-app-in-the-luis-portal

There's a couple of ways you can do this, and it really depends on your code. Basically, in the same place where you send the proactive message that User B has been found, you need to call dc.ContinueDialogAsync() or dc.RepromptDialogAsync(), as applicable.

That being said, I think the best option would be to split your Dialog. One Dialog gets User A in the queue. Once in, they are no longer in a dialog. Once User B is found, it sends User A the new Dialog.

I've more or less done this with Sample 16. Proactive Messages by:

1. Creating the Dialog to be called once User B is found
2. Under CreateCallback() (which is where this sample proactively sends a message), I added the following code to the end of that method (for some reason it doesn't want to format as code):

await turnContext.SendActivityAsync($"Job {jobInfo.TimeStamp} is complete.");

var dc = await Dialogs.CreateContextAsync(turnContext);

await dc.BeginDialogAsync(nameof(MyDialog));

Note: To test, I created a Dialog for User A after they "run" a job. The dialog sits there until User B completes the job. A new dialog was started for User A right after.

For you, this probably looks like:

There's a good chance that the reason this isn't working for you is because both of those links mention you need to create a New Collection in your CosmosDB resource in Azure. Microsoft recently updated the CosmosDB resource to require that new collections are made with Partition Keys, which aren't yet supported in Bot Framework. There's currently a Design Change Request to add this ability, but it's being stalled by the C# Cosmos SDK.

In the meantime, start by making the Cosmos resource in Azure and DO NOT make a database or collection. ONLY make the Cosmos resource. The bot framework SDK is set up to make a new DB and collection if the one you specify doesn't exist, and it can make one without partitions...so let the bot do the work here.

I used the second link you posted to change the Simple Prompt bot sample to work with Cosmos. Note: The endpoint and key are the default ones for the CosmosDB Emulator, which you can use to test locally, if you prefer.

Here is my startup.cs:

In your .bot file, a comma is missing between your 2 items in your services array. Should be like the following: