- What is the v4 SDK?
- Who is this for? Why should I use this SDK?
- What can I build with this SDK?
- What happens to my bot built using Bot Builder SDK v3?
- Where can I get help? Where do I report issues and feature requests?
- What are your code contribution guidelines?
- Is there a roadmap for this SDK? When will this be generally available?
What is the v4 SDK?
Bot Builder v4 SDK builds on the feedback and learnings from the prior Bot Builder SDKs. It introduces the right levels of abstraction while enabling rich componentization of the bot building blocks. You can start with a simple bot and grow your bot in sophistication using a modular and extensible framework.
Who is this for? Why should I use this SDK?
Bot Builder SDK v4 is for developers building bots using the Microsot Bot Framework. The SDK strives to keep simple things simple and make complex things possible. We are taking an open approach to building our v4 SDK together, with the community. See the Contribution Guidelines below to participate in this project.
What can I build with this SDK?
You can get started by building a very simple bot and then scale it all the way up to support different types of interactions with users. You can design freeform conversations in your bot. Your bot can also have more guided interactions where it provides the user discrete choices or actions. The conversation can use simple text strings or more complex rich cards containing text, images, and action buttons. And you can add natural language interactions to allow your users to interact with your bots in a natural and expressive way.
What happens to my bot built using Bot Builder SDK v3?
SDK V3 bots continue to run and be supported by Azure Bot Service. Since the release of Bot Framework SDK V4, as with other frameworks, we continue supporting SDK V3 with security, high priority bug fixes, and connector / protocol layer updates. Customers can expect v3 support to continue through 2019.
At this time, migration help for bots created with SDK V3 to SDK V4 will come in the form of documentations and samples. We currently do not have plans to provide any SDK V3 compatibility layer in SDK V4 that would allow V3 build bots to work within a V4 bot.
Read more about Bot Framework Frequently Asked Questions
Where can I get help? Where do I report issues and feature requests?
You can always get help by filing an issue on the appropriate GitHub issues page. Please remember to search issues to see if there already is a solution to what you are looking for.
- .Net SDK issues – https://github.com/Microsoft/botbuilder-dotnet/issues
- JS SDK issues – https://github.com/Microsoft/botbuilder-js/issues
- Python SDK issues - https://github.com/Microsoft/botbuilder-python/issues
- Java SDK issues - https://github.com/Microsoft/botbuilder-java/issues
What are your code contribution guidelines?
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com. When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g. label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
Is there a roadmap for this SDK? When will this be generally available?
We typically look out 3 to 6 months to establish a set of investment areas we want to work towards. Please see the Roadmap for more details.