New dependencies on OWIN, HttpListener and WebAPI

[dcherubini]

With previous version of the media bot SDK, the process running the SDK also needs to expose an HTTPS endpoint in order to receive notifications from the Microsoft Teams' servers regarding any updates happening inside the call (e.g., participants joining and leaving, the meeting ending, etc.).

For example, the IncidentBot sample is using the now deprecated Microsoft.AspNetCore package to create a web host and MVC controllers to process the notifications.

With the release of the SDK version 1.26.0.94, the .NET Framework version now has multiple new dependencies:

• Microsoft.AspNet.WebApi.Client (>= 5.2.7)
• Microsoft.AspNet.WebApi.Core (>= 5.2.7)
• Microsoft.AspNet.WebApi.Owin (>= 5.2.7)
• Microsoft.Owin (>= 4.2.2)
• Microsoft.Owin.Host.HttpListener (>= 4.2.2)
• Microsoft.Owin.Hosting (>= 4.2.2)
• Unity (>= 5.11.10)

Leaving aside the Unity container, the rest of the dependencies seem to indicate that the SDK is now able to start a self-hosted WebAPI inside the bot process. What I'm interested in is if the SDK now provides a way of running this HTTPS endpoint by itself, or if the process still needs to implement this endpoint? If not, then what is the purpose of those new SDK dependencies?

[ssulzer]

@dcherubini Regardless of the new dependencies of the Microsoft.Skype.Bots.Media library, the bot application must continue to host an HTTPS endpoint to receive incoming call/meeting invitations + meeting roster notifications. So no change in the bot application picking up this new media library. Thanks.