Bot Framework：将 DialogContext 传递给 ContinueConversationAsync 回调方法

Question

I'm looking for a way to pass the DialogContext to the ContinueConversationAsync BotCallbackHandler method.

For example, when I am inside a childDialog, the DialogContext dc in the ContinueDialogAsync method of the childDialog shows correctly 2 dialogs on the stack (childDialog[0] + rootDialog[1]).

public override async Task<DialogTurnResult> ContinueDialogAsync(DialogContext dc, CancellationToken cancellationToken = default)

I am trying to access the same DialogContext from an API call using the ContinueConversationAsync BotCallbackHandler method.

await ((BotAdapter)_adapter).ContinueConversationAsync(_appId, conversationReference, BotCallback, default(CancellationToken));

When constructing a DialogContext as coded below in the BotCallbackHandler method, I can use it to start a new Dialog using BeginDialogAsync . However, I am missing the existing childDialog on the stack which indicates the bot's current context. I am always getting only the rootDialog[0] on the stack, but not the childDialog which my bot is currently processing.

private async Task BotCallback(ITurnContext turnContext, CancellationToken cancellationToken)
{
   var conversationStateAccessors = conversationState.CreateProperty<DialogState>(nameof(DialogState));
   var dialogSet = new DialogSet(conversationStateAccessors);
   Dialog rootDialog Dialog = new RootDialog();
   dialogSet.Add(rootDialog);
   Dialog childDialog = new ChildDialog();
   dialogSet.Add(childDialog);
   var dialogContext = await dialogSet.CreateContextAsync(turnContext, cancellationToken);

   //end the most recent dialog on the stack, which should bring the conversation back to the parent root dialog
   var results = await dialogContext.EndDialogAsync();
}

My goal is to be able to end the active childDialog which is the highest up the stack, to bring back the conversation to the parent dialog. How can I retrieve this DialogContext in the CallBack method?

Answer 1

Your case sounds like a good opportunity to use ActivityPrompt . It's an abstract class so you'll have to derive from it. The idea is that prompts already have "retry prompts" built into them, which means the dialog will keep telling the user that it's waiting for one specific thing when the user tries to talk to the bot. In your case, the prompt could waiting for a special activity that only gets sent to your bot when the long-running process ends. This may be more intuitive than trying to manually end the dialog from outside of it.