corebot | A bot to trigger Rundeck and Jenkins jobs from Slack | Bot library

If the ib and ob values displayed by the *.bot endpoint are false this means the bot and the Direct Line app service extension are unable to connect to each other.

Make sure you verify below things:

1. Double check the code for using named pipes has been added to the bot.
2. Confirm the bot is able to start up and run at all. Useful tools are Test in WebChat, connecting an additional channel, remote debugging, or logging.
3. Restart the entire Azure App Service the bot is hosted within, to ensure a clean start up of all processes.

Please check troubleshooting guide, it seems updated today. (still old date reflected some how, not sure why)

The Bot Framework has significantly changed between version 3 and version 4. November 2019, the Bot Framework V4 SDK went generally available.

The following documentation could help understanding the differences between v3 and v4 bots.

• Migration overview

• Differences between the v3 and v4 .NET SDK

• Migrate a .NET v3 bot to a .NET Framework v4 bot

• Migrate a .NET v3 bot to a .NET Core v4 bot

Your setup is odd...you're making your ChitChatRecognizer, which is a bot (it derives from ActivityHandler), and then later DI into either a dialog or another bot, I imagine? Also it seems you want to treat QnAMaker (the recognizer for QnA) as a singleton, but you initialize it in OnMessageActivityAsync--meaning it won't initialize unless your bot receives a message activity, so if you're trying to initialize something else the requires a QnAMaker, it won't exist on startup.

Anyways, to answer the question of how do you insert QnAMakerinto corebot, if you wanted to add QnAMaker as a singleton, you can add it as singleton in startup, then call it from your bot code when you need to make a call to QnAMaker.

Add QnAMaker to Corebot Sample

In Startup.ConfigureServices:

Defining multiple bots in the same project is not possible. You can only attach one implementation to the IBot interface. Additionally when the project is deployed, its URL will only be recognized as one bot. You can extend the capabilities of your bot by adding more controllers but it will still register as a single bot.

If you still want to do this somehow, I'd suggest creating a menu context as the initial response of your bot. Give the user an option of choosing what functionality (different bot) they are going to use. From that point just separate the flows throughout your bot.

Your issue looks related to the name of the event. The WebChat is sending an event named requestWelcomeDialog, where your bot code is looking for an event named webchat/join. If you change one of them, it should work.

There are two possibilities for handling welcome messages.

1. Conversation Update. DirectLine broadcasts a conversation update event by default, however this is not preferred. This event will end up in OnMembersAddedAsync.

2. Custom Event. Send a custom event using WebChat v4, as described in this sample. This event will end up in OnEventActivityAsync.

My advice would be to upgrade to the new WebChat (v4) and to have a look at this sample. The ConversationUpdate has limitations and you are more flexible by sending a custom event.

The V4 MessageController should rarely, if ever, change from the skeleton. In this line:

You need to add MyDialog to dialog list in MainDialog. In you MainDialog you need to inject MyDialog instance and add it to dialog list using AddDialog(mydialoginstance);

Similar to how you have added bookingDialog