Botbuilder-dotnet: Proactive Messaging ContinueConversationAsync is not usable without AppId

[MarekLani]

Version

4.2.2.0

Describe the bug

Adapter.ContinueConversationAsync method requires AppId not to be empty. This behavior is not in pair with Node.js SDK where the proactive messaging works without providing AppID when calling continueConvrrsationAsync. Based on investigation of Node.js SDK, AppID should even not be input parameter for ContinueConversationAsync, as it should be resolved by framework itself.

To Reproduce

See above

Expected behavior

Parity with Node.js SDK

[bug]

[ceciliaavila]

Hi @Stevenic,
If you agree, we can help you tackle this issue. We have been analyzing it and we found a possible solution that does not introduce breaking changes.

[Stevenic]

This issue is on the C# side of things and has to do with the fact the C# adapter wants to support multiple bots for a single adapter. The JS adapter is designed such that you need a separate adapter for each bot.

[cleemullins]

I think the existing behavior here is Fine for us to live with for this iteration.

[cleemullins]

As Steven said, the design goals of the adapters are different. I'm going to close this as "By Design" at this time.