Ported 3.13.0.3

• Merged microsoft/botframework-sdk@e927e34
• Fixed microsoft/botframework-sdk#2515

Ported 3.12.5

• Merged microsoft/botframework-sdk@c5689fb

Ported 3.11.1-int01

• Merged microsoft/botframework-sdk@ba60581
• Upgraded ASP.NET Core package dependencies to v2.0.0. You need to upgrade your client's ASP.NET Core package versions to consume the library.
• Now Bot Connector targets at net45, netstandard1.6 and netstandard2.0.

Ported 3.11.0

Rebuilt the packages. It seems that the packages of the previous version still have dependencies on Microsoft's official ones. #2

Synchronized version numbers of the packages. Still, I increased the revision number of

• Microsoft.Bot.Builder.Calling
• Microsoft.Bot.Builder.FormFlow.Json
• Microsoft.Bot.Builder.History

so I can upload the fixed packages to NuGet.

The packages of previous version has been unlisted from NuGet.

Ported 3.9.1

This release has incorrect dependencies and has been unlisted from NuGet. See the next release for more information.

Imported from microsoft/botframework-sdk#3472. Remastered the polyfill code.

The packages are available on NuGet. Note the versions of the packages are kept the same as Microsoft's. To reduce confusion, I have unlisted some of the previously released "v3.8.1" packages (e.g. Bot.Builder.FormFlow.Json).

• The libraries are targeted at net45/netstandard1.6 or net46/netstandard2.0.
  • You need .NET Core 1.0 / .NET Framework 4.5 to consume Bot.Connector package.
  • You need .NET Core 2.0 / .NET Framework 4.6 to consume Bot.Builder packages.
• The new branch is more robust to the modifications on Microsoft's original repos.
• Now you can use EXACTLY the same code for .NET Framework and .NET Core, except
  • In ASP.NET Core, there is no ConfigurationManager, so I added SettingsUtils.AttachConfiguration and you need to call it upon initialization of the website (e.g. in Startup.ConfigureServices).

This is an unofficial port. By using the packages, you understand that the released packages can be buggy. For more information, see the Repository Wiki.

Ported Microsoft.Bot.Builder 3.9.0 [int0]

Target .NET Standard 2.0. Build your bots with ASP.NET Core 2.0!

• Use BinaryFormatter to take over JsonSerializer. Now you can write your model classes exactly in the same way as the official documentation.

• Add a IConfiguration parameter for configuration injection in Conversation class. You need to change the registration code. See Microsoft.Bot.Sample.AspNetCore.AnnotatedSandwichBot for example.

• I have only tested EchoBot and AnnotatedSandwichBot. There is some LUIS issue with the rest bot examples, namely, their quota is used up. According to the API response, we need to wait for ~3d18h before the quota can be replenished.

  • Thus, this pre-release may still be buggy
  • And I haven't tested if Regex can be successfully serialized.

Ported Microsoft.Bot.Builder 3.8.1 r1

No major changes, almost.

See commit history for details.

Ported Microsoft.Bot.Builder 3.8.1

See /~https://github.com/Microsoft/BotBuilder/releases for MS's release notes.

---

Updated the ported version to Microsoft.Bot.Builder 3.8.1, along with Microsoft.Bot.Connector.

I decided to unify the version numbers of all the components, making it consistent with the version of Microsoft.Bot.Builder. That means we now have v3.8.1 of CXuesong.Ported.Microsoft.Bot.Connector.AspNetCore, not v3.6.0-alpha.

Microsoft.Bot.Builder.FormFlow.Json.Standard remains unchanged since v3.5.1-int1, because there's no update from MS's repos. I only stripped pre-release tag off.