569f6a523e
* Adds check to TranscriptLoggerMiddleware doesn't log contine conversation event activities. Changes include: - Added check in TranscriptLoggerMiddleware to filter incoming ContinueConversation events. - Introduced EventActivityNames class with constant strings for ContinueConversation so we don't have those strings hardcoded. - Added also CreateConversation to the EventActivityNames helper (not related to this issue but saw it and decided to add it since it is better to have constants). - Refactored ConversationReferenceEx to use the new constant (and use more straightforward code to create the event). - Added tests for new logic in TranscriptLoggerMiddleware. - Updated Skills testing projects to use the new constant * Renamed EventActivityNames to ActivityEventNames * Updated a couple of files that I missed after the rename. |
||
---|---|---|
.github | ||
.vscode | ||
FunctionalTests | ||
build | ||
doc | ||
libraries | ||
recognizers-text/Utterance Changes | ||
specs | ||
tests | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
BotBuilder-DotNet.ruleset | ||
CODE_OF_CONDUCT.md | ||
Changes.md | ||
CodeCoverage.runsettings | ||
Contributing.md | ||
Directory.Build.props | ||
LICENSE | ||
Microsoft.Bot.Builder.Skills.sln | ||
Microsoft.Bot.Builder.sln | ||
README.md | ||
UsingMyGet.md | ||
_config.yml | ||
bot.png | ||
bot_icon.png | ||
installbf.cmd |
README.md
What's new with Bot Framework
This repository contains code for the .NET version of the Microsoft Bot Framework SDK, which is part of the Microsoft Bot Framework - a comprehensive framework for building enterprise-grade conversational AI experiences.
This SDK enables developers to model conversation and build sophisticated bot applications using .NET. SDKs for JavaScript, Python and Java (preview) are also available.
To get started building bots using the SDK, see the Azure Bot Service Documentation.
For more information jump to a section below.
- Build status
- Packages
- Getting started
- Getting support and providing feedback
- Contributing and our code of conduct
- Reporting security sssues
Build Status
Branch | Description | Build Status | Coverage Status | Windows Bot Test Status | Linux Bot Test Status |
---|---|---|---|---|---|
Main | 4.11.* Preview Builds |
Packages
Daily Feeds
The daily feeds are published to Azure Artifacts and MyGet.
- The Azure Artifacts daily feed is our preferred method to obtain the most recent Bot Framework NuGet packages. To use the daily builds published to Azure Artifacts, use:
https://pkgs.dev.azure.com/ConversationalAI/BotFramework/_packaging/SDK/nuget/v3/index.json
For instructions to add the feed to your NuGet configuration, visit this page.
- To use the daily builds published to MyGet, please follow the instructions here. NOTE: The MyGet feed will be depecrated soon. Please use the Azure Artifacts daily feed instead.
Dependency Graph
To view our libraries' interdependencies, you can refer to the dependency graph for our libraries.
Getting Started
To get started building bots using the SDK, see the Azure Bot Service Documentation.
The Bot Framework Samples includes a rich set of samples repository.
If you want to debug an issue, would like to contribute, or understand how the Bot Builder SDK works, instructions for building and testing the SDK are below.
Prerequisites
Clone
Clone a copy of the repo:
git clone https://github.com/Microsoft/botbuilder-dotnet.git
Change to the SDK's directory:
cd botbuilder-dotnet
Build and test locally
Open Microsoft.Bot.Builder.sln
in Visual Studio.
On the menu bar, choose Build > Build Solution.
When the solution is built, local NuGet package files (.nupkg) are generated for each project and are available under the outputPackages
directory. You can add this folder to your NuGet Package Manager source list in Visual Studio (choose Tools > NuGet Package Manager > Package Manager Settings from the Visual Studio menu and add an additional Package Sources from there), allowing you to consume these in your local projects.
Getting support and providing feedback
Below are the various channels that are available to you for obtaining support and providing feedback. Please pay carful attention to which channel should be used for which type of content. e.g. general "how do I..." questions should be asked on Stack Overflow, Twitter or Gitter, with GitHub issues being for feature requests and bug reports.
Github issues
Github issues should be used for bugs and feature requests.
Stack overflow
Stack Overflow is a great place for getting high-quality answers. Our support team, as well as many of our community members are already on Stack Overflow providing answers to 'how-to' questions.
Azure Support
If you issues relates to Azure Bot Service, you can take advantage of the available Azure support options.
We use the @botframework account on twitter for announcements and members from the development team watch for tweets for @botframework.
Gitter Chat Room
The Gitter Channel provides a place where the Community can get together and collaborate.
Contributing and our code of conduct
We welcome contributions and suggestions. Please see our contributing guidelines for more information.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Reporting Security Issues
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT License.