Application<TState> Class

Creates a new Application instance.

Fluent interface for accessing the bot adapter used to configure the application.

Fluent interface for accessing Adaptive Card specific features.

Fluent interface for accessing AI specific features.

Accessing authentication specific features.

Fluent interface for accessing Meetings' specific features.

Fluent interface for accessing Message Extensions' specific features.

The application's configured options.

Fluent interface for accessing Task Modules' specific features.

Adds a new route to the application.

Developers won't typically need to call this method directly as it's used internally by all of the fluent interfaces to register routes for their specific activity types.

Routes will be matched in the order they're added to the application. The first selector to return true when an activity is received will have its handler called.

Invoke-based activities receive special treatment and are matched separately as they typically have shorter execution timeouts.

If the user is signed in, get the access token. If not, triggers the sign in flow for the provided authentication setting name and returns.In this case, the bot should end the turn until the sign in flow is completed.

Handles incoming activities of a given type.

Handles incoming activities of a given type.

Handles incoming activities of a given type.

Handles incoming activities of a given type.

Add a handler that will execute after the turn's activity handler logic is processed.
Handler returns true to finish execution of the current turn. Handler returning false prevents the bots state from being saved.

Add a handler that will execute before the turn's activity handler logic is processed.
Handler returns true to continue execution of the current turn. Handler returning false prevents the turn from running, but the bots state is still saved, which lets you track the reason why the turn was not processed. It also means you can use this as a way to call into the dialog system. For example, you could use the OAuthPrompt to sign the user in before allowing the AI system to run.

Handles config fetch events for Microsoft Teams.

Handles config submit events for Microsoft Teams.

Handles conversation update events.

Handles conversation update events.

Handles when a file consent card is accepted by the user.

Handles when a file consent card is declined by the user.

Handles incoming messages with a given keyword.
This method provides a simple way to have a bot respond anytime a user sends your bot a message with a specific word or phrase.

Handles incoming messages with a given keyword.
This method provides a simple way to have a bot respond anytime a user sends your bot a message with a specific word or phrase.
For example, you can easily clear the current conversation anytime a user sends "/reset":
application.OnMessage(new Regex("reset"), (context, turnState, _) => ...);

Handles incoming messages with a given keyword.
This method provides a simple way to have a bot respond anytime a user sends your bot a message with a specific word or phrase.

Handles incoming messages with a given keyword.
This method provides a simple way to have a bot respond anytime a user sends your bot a message with a specific word or phrase.
For example, you can easily clear the current conversation anytime a user sends "/reset":
application.OnMessage("/reset", (context, turnState, _) => ...);

Handles message soft delete events.

Handles message edit events.

Handles message reactions added events.

Handles message reactions removed events.

Handles message undo soft delete events.

Handles O365 Connector Card Action activities.

Handles read receipt events for messages sent by the bot in personal scope.

Called by the adapter (for example, a CloudAdapter) at runtime in order to process an inbound Activity.

Manually start a timer to periodically send "typing" activities.

Manually stop the typing timer.