Conversation
Add .NET solution for extensible bot activity schemas with modern serialization, extension data, and reply support. Includes CI workflow, semantic versioning, and comprehensive unit tests for schema evolution and custom fields.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Added a permissions section to the Core-CI workflow, granting read access to repository contents and write access to pull-requests. This explicitly defines the workflow's required permissions.
heyitsaamir
reviewed
Dec 10, 2025
| /// </summary> | ||
| public static readonly JsonSerializerOptions DefaultJsonOptions = new() | ||
| { | ||
| WriteIndented = true, |
Collaborator
There was a problem hiding this comment.
Putting this at the bottom most layer means that more space will be used up in the payload
Member
Author
There was a problem hiding this comment.
yes, but not too much. I think it's ok for now
| /// The reply activity automatically swaps the From and Recipient accounts and preserves | ||
| /// the conversation context, channel ID, and service URL from the original activity. | ||
| /// </remarks> | ||
| public CoreActivity CreateReplyActivity(string text = "") |
Collaborator
There was a problem hiding this comment.
Adding a note: Should this exist here or be in the client layer?
Member
Author
There was a problem hiding this comment.
added a new optional param to set the type
This pull request introduces several new sample bots and supporting infrastructure to the `core` directory, demonstrating different usage scenarios for the Microsoft.Bot.Core SDK. It also adds compatibility support for legacy Bot Framework bots, improves development environment configuration, and updates documentation and gitignore settings. **New sample bots and scenarios:** - Added three new sample projects: - [`CompatBot`](diffhunk://#diff-22411d9bef78e3d139f1e4b1a4d5e047bb26428a97bf59df7f5b983e584babd8R1-R13): Demonstrates running a legacy Bot Framework bot using the new compatibility layer, including `EchoBot` implementation and required configuration files. [[1]](diffhunk://#diff-22411d9bef78e3d139f1e4b1a4d5e047bb26428a97bf59df7f5b983e584babd8R1-R13) [[2]](diffhunk://#diff-b9be640e365d9187b0d1a2021dddb84311b737f8c28b16428e3b2a450a4f331aR1-R35) [[3]](diffhunk://#diff-62be1f70aaabb519334fe39cd50c0e25a98717ebb9fab85b688832917c9c75bbR1-R29) [[4]](diffhunk://#diff-834a6cbae004839d32944b2f2a3cf8edc3a32f558597d464401178fa95781edcR1-R9) - [`CoreBot`](diffhunk://#diff-1087baf076a83b00d0c97ef01c02174668cb26c9fad5d2c33284e0889150ed65R1-R13): Shows a simple bot using the new SDK, with configuration and logging settings. [[1]](diffhunk://#diff-1087baf076a83b00d0c97ef01c02174668cb26c9fad5d2c33284e0889150ed65R1-R13) [[2]](diffhunk://#diff-b94b53965e9052345453f2ab6bec21420a36c4b67c9a6c568b9c80edcd0882d1R1-R22) [[3]](diffhunk://#diff-84b21a8c78e12fee4df3b2d67483407632a1fe5d25691ed7cfefde85adc92a25R1-R11) - [`Proactive`](diffhunk://#diff-ffe34fac742569e7a6cfb5589871a8b9571c7692f6af33e167f39cc2b8be3ed3R1-R17): Demonstrates sending proactive messages using a background worker. [[1]](diffhunk://#diff-ffe34fac742569e7a6cfb5589871a8b9571c7692f6af33e167f39cc2b8be3ed3R1-R17) [[2]](diffhunk://#diff-f32e1fd30a40c5aa42855895485dbb9c8b79d4029cd3db1a1446f48846f8604dR1-R10) [[3]](diffhunk://#diff-61d7e83f772e536a1729f5c12b1b028a2a396a28e2175541489e85d89d2758ecR1-R31) [[4]](diffhunk://#diff-1342c159b3ce809afd5880d58bd2f17e3eeade347f10d5b8d6d550cb3a0ab8f9R1-R8) - Added scenario scripts for middleware and proactive messaging, runnable via dotnet script. [[1]](diffhunk://#diff-aee4a2e56fbce4adfe46afec84a447a9aab7752f7c24982b51b8475af942124fR1-R34) [[2]](diffhunk://#diff-8287e53b5a4e259703b929262b11fdb5f783564de364cc184d27a5b7486de729R1-R43) - Provided an example `launchSettings.json` for local development of scenarios. **Compatibility support:** - Introduced `CompatAdapter` and related classes to bridge new bot application models with legacy Bot Framework interfaces, enabling easier migration and integration of existing bots. [[1]](diffhunk://#diff-ee802b583e856949e14f231284969979f8827efaa484f0b431badb7936809855R1-R116) [[2]](diffhunk://#diff-e70e201729b0f386ddb70a5d3f83751f2bd0a08e527b0a5265fbb8094a9abe19R1-R27) **Development environment and documentation improvements:** - Updated `.devcontainer/devcontainer.json` to add Docker-in-Docker, .NET 10, and ensure latest feature versions for improved local development experience. - Added a `README.md` with instructions for testing and running scenarios. - Added common development files to `.gitignore` and included it in the solution. [[1]](diffhunk://#diff-af85f59c6492668dca14d5f06b54cc2c3173708c83073e1d947b4c007dc851d6R1-R2) [[2]](diffhunk://#diff-19ad97af5c1b7109a9c62f830310091f393489def210b9ec1ffce152b8bf958cR4-R12) **Solution structure updates:** - Updated `core.slnx` to include new sample projects and `.gitignore` as solution items. --- **New sample bots and scenarios:** - Added `CompatBot`, `CoreBot`, and `Proactive` sample projects with implementations and configuration files to demonstrate different SDK usage scenarios. [[1]](diffhunk://#diff-22411d9bef78e3d139f1e4b1a4d5e047bb26428a97bf59df7f5b983e584babd8R1-R13) [[2]](diffhunk://#diff-b9be640e365d9187b0d1a2021dddb84311b737f8c28b16428e3b2a450a4f331aR1-R35) [[3]](diffhunk://#diff-62be1f70aaabb519334fe39cd50c0e25a98717ebb9fab85b688832917c9c75bbR1-R29) [[4]](diffhunk://#diff-834a6cbae004839d32944b2f2a3cf8edc3a32f558597d464401178fa95781edcR1-R9) [[5]](diffhunk://#diff-1087baf076a83b00d0c97ef01c02174668cb26c9fad5d2c33284e0889150ed65R1-R13) [[6]](diffhunk://#diff-b94b53965e9052345453f2ab6bec21420a36c4b67c9a6c568b9c80edcd0882d1R1-R22) [[7]](diffhunk://#diff-84b21a8c78e12fee4df3b2d67483407632a1fe5d25691ed7cfefde85adc92a25R1-R11) [[8]](diffhunk://#diff-ffe34fac742569e7a6cfb5589871a8b9571c7692f6af33e167f39cc2b8be3ed3R1-R17) [[9]](diffhunk://#diff-f32e1fd30a40c5aa42855895485dbb9c8b79d4029cd3db1a1446f48846f8604dR1-R10) [[10]](diffhunk://#diff-61d7e83f772e536a1729f5c12b1b028a2a396a28e2175541489e85d89d2758ecR1-R31) [[11]](diffhunk://#diff-1342c159b3ce809afd5880d58bd2f17e3eeade347f10d5b8d6d550cb3a0ab8f9R1-R8) - Added scenario scripts for middleware and proactive messaging, plus an example launch settings file for local testing. [[1]](diffhunk://#diff-aee4a2e56fbce4adfe46afec84a447a9aab7752f7c24982b51b8475af942124fR1-R34) [[2]](diffhunk://#diff-8287e53b5a4e259703b929262b11fdb5f783564de364cc184d27a5b7486de729R1-R43) [[3]](diffhunk://#diff-19cd1809f42bd0d871748a1e3bf7c705961f9abd0a4da67acc547f42c1ebfcd6R1-R20) **Compatibility support:** - Introduced `CompatAdapter` and `CompatActivity` to support running legacy Bot Framework bots with the new SDK. [[1]](diffhunk://#diff-ee802b583e856949e14f231284969979f8827efaa484f0b431badb7936809855R1-R116) [[2]](diffhunk://#diff-e70e201729b0f386ddb70a5d3f83751f2bd0a08e527b0a5265fbb8094a9abe19R1-R27) **Development environment and documentation:** - Enhanced `.devcontainer` with Docker-in-Docker, .NET 10, and latest feature versions for improved local development. - Added a `README.md` with setup and testing instructions. - Updated `.gitignore` and included it in the solution for better source control hygiene. [[1]](diffhunk://#diff-af85f59c6492668dca14d5f06b54cc2c3173708c83073e1d947b4c007dc851d6R1-R2) [[2]](diffhunk://#diff-19ad97af5c1b7109a9c62f830310091f393489def210b9ec1ffce152b8bf958cR4-R12) **Solution structure:** - Updated `core.slnx` to include new projects and configuration files. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: rido-min <14916339+rido-min@users.noreply.github.com>
Updated Azure DevOps pipeline to trigger only on next/* branches and use ubuntu-22.04. Added cd-core.yaml to solution items in core.slnx. Removed null-forgiving operator from CoreActivity.cs return statement for safer null handling.
Added a UseDotNet@2 task to install .NET 8 SDK (8.0.x) before the .NET 10 SDK in the BuildTestPack job. This ensures both SDK versions are available for build and test processes.
Changed package icon to bot_icon.png in project properties. Added ItemGroup to explicitly include bot_icon.png and README.md at the root of the NuGet package during packing.
Added a new bot_icon.png file to the project, providing a graphical asset that can be used as an icon or visual element within the application.
Changed the pipeline condition so that NuGet packages are pushed only when building from the refs/heads/next/core branch, instead of the main branch. This restricts package publishing to the next/core branch.
Ignored launchSettings.json, appsettings.Development.json, and .runsettings to prevent tracking of local configuration and test settings files.
Introduce Microsoft.Bot.Core.Tests targeting .NET 10.0 with xUnit and code coverage. Add core-test.yaml workflow to run these tests with Azure AD credentials. Update solution file to include new test project and workflow. Implement ConversationClientTest for Teams activity scenarios. Update core-ci.yaml to run only unit tests.
Updated the build pipeline to run tests only for the Microsoft.Bot.Core.UnitTests project. Changed environment variable to "TEST_CONVERSATIONID" in ConversationClientTest.cs and corrected the hardcoded conversation ID format by removing the message ID suffix.
- Prefix echo replies with "Echo from BF Compat" - Change default log level to Warning; add Debug for Microsoft.Bot - Remove using statement for TurnContext in CompatAdapter - Expand exception handling to rethrow non-HttpOperationException - Add debug/info logging to BotApplication activity processing
Introduce .editorconfig for code style and nullable strictness. Update solution to include .editorconfig. Rename CoreActivity.CreateReplyActivity to CreateReplyMessageActivity and update all usages. Extend CoreActivityJsonContext for Int64/Double support. Apply minor formatting fixes and missing braces. Strengthen and update unit tests for new property types and method changes.
Replaced all var declarations with explicit types across the codebase, including tests, bot implementations, and entry points. This improves code clarity and type safety, making variable types more visible and aiding maintainability. No functional changes were made.
Added copyright and MIT license headers to all source and test files. Updated .editorconfig to enforce file header template for new files. Made minor code style improvements and access modifier updates. Ensured consistent attribution and licensing across the codebase.
EchoBot now informs users how to trigger a proactive message via a new `/api/notify/{conversationId}` endpoint. Added a GET endpoint to send proactive messages to a conversation by ID. Updated message handling to support CancellationToken and included necessary usings for proactive messaging support.
Integrate Azure Monitor Application Insights telemetry into both CompatBot and CoreBot using OpenTelemetry. Update appsettings.json to include a placeholder Application Insights connection string and adjust logging levels for better diagnostics. Refactor EchoBot to accept an ILogger and log version info; comment out some unused message handlers. Improve CoreBot reply robustness by safely extracting conversation type. Reformat project files for consistency and explicitly add Azure Monitor package. Update Proactive Worker to use constants for ServiceUrl and FromId. Refactor ConversationClient to use StringContent for activity payloads, ensuring correct JSON serialization and content type.
Removed unnecessary using directives from EchoBot.cs and ConversationClient.cs. Updated TryGetValue in Program.cs to use object? for better type safety and clarity.
Refactored pipeline triggers to use path filters for PRs, targeting only core/** changes. Removed obsolete trigger config and comments. Introduced PushToADOFeed variable to control NuGet push step, replacing branch-based condition.
Reorganize and clean up using directives across the codebase for consistency. In CompatBotAdapter, add indented JSON logging for InvokeResponse bodies, set HTTP status code from InvokeResponse.Status, and serialize only the response body. Update EchoBot to return an object for InvokeResponse body instead of a plain string. No core logic changes; improves maintainability and debugging.
This pull request improves code documentation throughout the Teams Bot Core and Compat libraries by enhancing XML doc comments for public classes, methods, and delegates. The changes clarify parameter purposes, return values, and overall behavior, making the codebase easier to understand and maintain for future developers. **Handler and Delegate Documentation Enhancements:** - Clarified XML documentation for handler delegates and argument classes in `ConversationUpdateHandler`, `InstallationUpdateHandler`, and `MessageReactionHandler`, specifying when handlers are invoked and detailing parameter and return value meanings. [[1]](diffhunk://#diff-520cbb31ec22b8f40b880f8c77056df61219382f41d4289fcf134ad376a477deL11-R22) [[2]](diffhunk://#diff-6a0ee37c3ed365cc18112bb823e064a58701192a6e6ddc95865cbd699b222826L9-R20) [[3]](diffhunk://#diff-f30f2a2f8907b41aea7962bdc2c935a725bf979ef8b99bc70379ed812e7dfcfeL11-R22) **Schema Entity Documentation Improvements:** - Expanded and clarified doc comments for methods and constructors in `ClientInfoEntity` and `MentionEntity`, explaining their purpose, parameter details, and return values. [[1]](diffhunk://#diff-41817d17ebfa1173983b9643204188f79cb2d675826bbdc28a385c5b42abd0b8L15-R22) [[2]](diffhunk://#diff-41817d17ebfa1173983b9643204188f79cb2d675826bbdc28a385c5b42abd0b8L35-R38) [[3]](diffhunk://#diff-41817d17ebfa1173983b9643204188f79cb2d675826bbdc28a385c5b42abd0b8L67-R72) [[4]](diffhunk://#diff-d2747143a751ee3809c1a3fe862ce6cec756f4ef1a94d1d91e9a4d63a70ef819L32-R38) [[5]](diffhunk://#diff-d2747143a751ee3809c1a3fe862ce6cec756f4ef1a94d1d91e9a4d63a70ef819L70-R71) **Compat Layer Documentation Updates:** - Added or improved XML documentation for key methods in `CompatAdapter`, `CompatBotAdapter`, and `CompatAdapterMiddleware`, including parameter requirements, operation descriptions, and return value details. [[1]](diffhunk://#diff-e6d701ce121dda6651c0dea00498d45e2cc0b0cec446a578f3058be691c7c0f5L57-R61) [[2]](diffhunk://#diff-c443812ac75b10f0cb9e0929a1165dee72b7c96adbd232d830a65348ccd1b42bL23-R34) [[3]](diffhunk://#diff-c443812ac75b10f0cb9e0929a1165dee72b7c96adbd232d830a65348ccd1b42bL43-R50) [[4]](diffhunk://#diff-c443812ac75b10f0cb9e0929a1165dee72b7c96adbd232d830a65348ccd1b42bL81-R91) [[5]](diffhunk://#diff-80a974c881b9ff3a697fe5b07985c8f55edb2e2896384d6d437a3e8dfa5a2817R11-R30) - Introduced a comprehensive class-level summary for `CompatConnectorClient`, clarifying its purpose as a stub for Bot Framework compatibility. **Invoke Response Documentation:** - Enhanced the summary and remarks for `CoreInvokeResponse` to clarify its role and typical usage in Adaptive Card and task module scenarios. --------- Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
#272) Changed the `FromCompatActivity` extension method to return a `CoreActivity` directly from a `Bot.Schema.Activity` since it's better at handling unknown values (like entities).
Added a routing system and typed context support enabling type-safe activity handling with pattern matching. **Main changes:** - Added `Route<TActivity>` and `Router` classes for declarative route registration - Added `MessageActivity` class extending `TeamsActivity` with message-specific properties - Updated `Context` to support generic `Context<TActivity>` for type-safe activity handling - Refactored `MessageHandler` to use the new routing system - Removed handler classes (`ConversationUpdateHandler`, `InstallationUpdateHandler`, `MessageReactionHandler`) , will update in future - Updated TeamsBot sample to demonstrate the new routing pattern - Added MessageActivityTests
This pull request introduces a comprehensive compatibility layer between the Bot Framework TeamsInfo API and the Teams Bot Core SDK, along with several supporting enhancements and documentation. The main focus is to provide seamless mapping and conversion between Bot Framework and Core SDK models, ensuring feature parity and interoperability. The changes include a detailed API mapping document, model enhancements for compatibility, new extension methods for type conversions, and some minor refactoring and bug fixes. **Key changes include:** ### 1. Compatibility Layer Documentation and API Mapping - Added `CompatTeamsInfo-API-Mapping.md`, a detailed document mapping all `CompatTeamsInfo` static methods to their corresponding REST endpoints and SDK client implementations, including usage examples, authentication, and model conversion strategies. ### 2. Model Enhancements for Teams Compatibility - Enhanced `TeamsConversationAccount` to extract and expose additional Teams-specific properties (`GivenName`, `Surname`, `Email`, `UserPrincipalName`, `UserRole`, `TenantId`) from the `Properties` dictionary, improving compatibility with the Bot Framework schema. [[1]](diffhunk://#diff-ab03c7985a1673a73536a9756293c78cba898a0de6197501e596ad144582a41aL38-R40) [[2]](diffhunk://#diff-ab03c7985a1673a73536a9756293c78cba898a0de6197501e596ad144582a41aL48-R133) - Updated `MeetingInfo` to use `TeamsConversationAccount` for the `Organizer` property instead of the more generic `ConversationAccount`, aligning with Bot Framework expectations. ### 3. Type Conversion Extension Methods - Added multiple extension methods in `CompatActivity.cs` for converting between Core SDK and Bot Framework types, including `TeamsChannelAccount`, `MeetingInfo`, `TeamsMeetingParticipant`, `ChannelInfo`, and paged member results. These methods ensure smooth interoperability and data mapping between the two frameworks. [[1]](diffhunk://#diff-92ebcca71bdaad244e949c815cbf1152d5a3d814cc007052ae7ad2dd8ab225a9R7) [[2]](diffhunk://#diff-92ebcca71bdaad244e949c815cbf1152d5a3d814cc007052ae7ad2dd8ab225a9R112-R283) ### 4. Refactoring and Naming Consistency - Renamed internal variables and properties from `TeamsAPXClient` to `TeamsApiClient` for clarity and consistency in `TeamsBotApplication`. ### 5. Bug Fixes and Method Signature Updates - Changed the parameter type of `SendMeetingNotificationAsync` in `TeamsApiClient` to accept a `TargetedMeetingNotification` instead of a more generic base type, ensuring stricter type safety. These changes provide a robust foundation for supporting Bot Framework TeamsInfo APIs on top of the Teams Bot Core SDK, facilitating migration and interoperability for bot developers.
This pull request refactors the `CompatAdapter` and related middleware to use dependency injection for service resolution, improving maintainability and aligning with modern .NET practices. The main changes involve replacing constructor parameters with `IServiceProvider`, updating middleware to resolve dependencies, and enhancing logging in the `CompatBotAdapter`. **Dependency Injection Refactoring:** * `CompatAdapter` now receives an `IServiceProvider` in its constructor, and uses it to resolve `TeamsBotApplication` and `CompatBotAdapter` instead of receiving them directly as parameters. All usages of these services within the class have been updated accordingly. * `CompatAdapterMiddleware` now receives both the Bot Framework middleware and an `IServiceProvider`, enabling it to resolve required services such as `IHttpContextAccessor` and `ILogger`. **Middleware and Adapter Updates:** * Middleware instantiation in `CompatAdapter` is updated to pass the `IServiceProvider` to each `CompatAdapterMiddleware`, ensuring dependencies are available during middleware execution. * Within `CompatAdapterMiddleware`, the `CompatBotAdapter` is now constructed with resolved `IHttpContextAccessor` and `ILogger` instances, improving logging and context-awareness. **Logging Improvements:** * Enhanced logging in `CompatBotAdapter` to include HTTP status codes when sending invoke responses, and to avoid serialization if the response body is null. **General Code Modernization:** * Added missing `using` statements for dependency injection and logging namespaces in affected files. [[1]](diffhunk://#diff-e6d701ce121dda6651c0dea00498d45e2cc0b0cec446a578f3058be691c7c0f5R8) [[2]](diffhunk://#diff-80a974c881b9ff3a697fe5b07985c8f55edb2e2896384d6d437a3e8dfa5a2817R5-R6)
The CompatMiddlware Adapter was creating a new TurnContext, and that created problems with Middleware. Instead of trying to adapt the middlware, we can just run the BF Middleware pipeline
This pull request refactors and improves the bot application hosting and authentication pipeline. The main goals are to defer configuration reading until the service provider is built, avoid building the service provider during service registration (an anti-pattern), and improve logging flexibility and reliability. New options classes are introduced to cleanly pass configuration, and authentication/authorization registration is made safer and more robust. Key changes include: **Configuration and Options Refactoring:** * Introduced `BotClientOptions` and `AuthenticationSchemeOptions` classes to encapsulate bot client and authentication scheme configuration, deferring configuration reading until the service provider is available. [[1]](diffhunk://#diff-65196a45c43063ad64be1ce1c69cd1cf0ddcc2f8b999b5679d74bb6d4a610ff0R1-R20) [[2]](diffhunk://#diff-13be7f71b9314c04c36d3d24e99723628e236cfc008159b22f6d9a862f8c75e0R1-R20) * Refactored `AddTeamsBotApplication` and `AddBotClient<TClient>` to register options and avoid building the service provider during registration, using `AddOptions<T>().Configure<IConfiguration>()` instead. [[1]](diffhunk://#diff-a5c655bf5836d61efb23de5aba33c6dc81b61cabaf9341f68c9f2a28afc48b58L26-R47) [[2]](diffhunk://#diff-32c43eec964cc43a0cc857afbe1da981ec6000ac6c95c94aef469c4ce859ebe7L96-R163) * Updated MSAL configuration to pass the logger as a parameter and select configuration and logger from service descriptors if available, only building a temporary provider as a fallback. **Authentication and Authorization Pipeline:** * Refactored `AddAuthorization` to accept an optional logger and to select configuration and logger from service descriptors, only building a temporary provider if necessary. * Improved JWT Bearer authentication to resolve the logger from request services at runtime, ensuring correct logging context and using a `NullLogger` fallback. [[1]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70L106-R121) [[2]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70L127-R156) [[3]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70L145-R166) [[4]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70L156-R177) **Middleware and Endpoint Registration:** * Changed `UseBotApplication<TApp>` to operate on `IEndpointRouteBuilder` instead of `IApplicationBuilder`, improving flexibility and ensuring authentication/authorization middleware is added safely. **Logging Improvements:** * Ensured that loggers are created from `ILoggerFactory` if available, otherwise defaulting to `NullLogger`, and that logging is robust throughout the authentication and configuration process. [[1]](diffhunk://#diff-32c43eec964cc43a0cc857afbe1da981ec6000ac6c95c94aef469c4ce859ebe7L65-R81) [[2]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70L75-R102) [[3]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70L127-R156) **General Code Quality:** * Added missing `using` directives for LINQ and other dependencies. [[1]](diffhunk://#diff-32c43eec964cc43a0cc857afbe1da981ec6000ac6c95c94aef469c4ce859ebe7R4-R10) [[2]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70R5) These changes collectively improve the reliability, maintainability, and testability of the bot application hosting and authentication infrastructure. --- **Configuration and Options Refactoring:** - Introduced `BotClientOptions` and `AuthenticationSchemeOptions` classes for encapsulating bot client and authentication scheme configuration, deferring configuration reading until the service provider is available. [[1]](diffhunk://#diff-65196a45c43063ad64be1ce1c69cd1cf0ddcc2f8b999b5679d74bb6d4a610ff0R1-R20) [[2]](diffhunk://#diff-13be7f71b9314c04c36d3d24e99723628e236cfc008159b22f6d9a862f8c75e0R1-R20) - Refactored `AddTeamsBotApplication` and `AddBotClient<TClient>` to use options registration and avoid building the service provider during registration. [[1]](diffhunk://#diff-a5c655bf5836d61efb23de5aba33c6dc81b61cabaf9341f68c9f2a28afc48b58L26-R47) [[2]](diffhunk://#diff-32c43eec964cc43a0cc857afbe1da981ec6000ac6c95c94aef469c4ce859ebe7L96-R163) - Updated MSAL configuration to pass the logger as a parameter and to select configuration/logger from service descriptors, only building a temporary provider if necessary. **Authentication and Authorization Pipeline:** - Refactored `AddAuthorization` to accept an optional logger, select configuration/logger from service descriptors, and only build a temporary provider as a fallback. - Improved JWT Bearer authentication to resolve the logger from request services at runtime and use a `NullLogger` fallback, ensuring robust logging. [[1]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70L106-R121) [[2]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70L127-R156) [[3]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70L145-R166) [[4]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70L156-R177) **Middleware and Endpoint Registration:** - Changed `UseBotApplication<TApp>` to work with `IEndpointRouteBuilder` instead of `IApplicationBuilder`, ensuring authentication/authorization middleware is added correctly and improving endpoint mapping flexibility. **Logging Improvements:** - Ensured loggers are created from `ILoggerFactory` when available, otherwise using a `NullLogger`, and improved logging reliability throughout the configuration and authentication process. [[1]](diffhunk://#diff-32c43eec964cc43a0cc857afbe1da981ec6000ac6c95c94aef469c4ce859ebe7L65-R81) [[2]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70L75-R102) [[3]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70L127-R156) **General Code Quality:** - Added missing `using` directives for LINQ and other dependencies. [[1]](diffhunk://#diff-32c43eec964cc43a0cc857afbe1da981ec6000ac6c95c94aef469c4ce859ebe7R4-R10) [[2]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70R5)
**Key changes:** **Activity Handler Extensions and Delegates** - Added new handler delegates and extension methods for message update, message delete, and message reaction activities (`OnMessageUpdate`, `OnMessageDelete`, `OnMessageReaction`, `OnMessageReactionAdded`, `OnMessageReactionRemoved`), enabling straightforward registration of handlers for these Teams activity types. - Refactored the invoke handler to use a strongly-typed `Context<InvokeActivity>` and provided an `OnInvoke` extension method for registering invoke handlers. **Routing Infrastructure Enhancements** - Updated the `Route` and `Router` classes to support handler functions that can return a response (`HandlerWithReturn`) and added the `InvokeRouteWithReturn` and `DispatchWithReturnAsync` methods to enable this. - Changed route matching logic to use the `TeamsActivityType` string for more precise activity type matching. --------- Co-authored-by: Rido <rido-min@users.noreply.github.com>
Revert the Microsoft.Bot.Builder.Integration.AspNet.Core NuGet package version in Microsoft.Teams.Bot.Compat.csproj from 4.23.1 to 4.22.3. No other changes were made. --------- Co-authored-by: Kavin Singh <kavinsingh@microsoft.com>
MehakBindra
force-pushed
the
next/core
branch
from
9b16656 to
3d480b9
Compare
## Summary
Refactored and expanded CompatActivityTests to provide comprehensive
coverage of the `FromCompatActivity()` method,
including support for complex `SuggestedActions` payloads.
## Changes
### Test Structure:
- Refactored into component-based tests (12 total) organized by Activity
aspect:
- Core Properties (2 tests)
- Attachments (2 tests)
- Entities (2 tests)
- SuggestedActions (2 tests)
- ChannelData (2 tests)
- Integration/Round-trip (2 tests)
**Why?** Makes it easier to mock the `CompatAdapter.ContinueConversationAsync` method when testing. Without the interface, the class itself would first have to be mocked, which means all the underlying components will have to be configured by hand.
1. Keeps the same pattern as CloudAdapter 2. `TurnContext.Adapter` will reference the `CompatAdapter` and not just the `CompatBotAdapter` as it was before this change. This means the same adapter is used everywhere. 3. Updated `ContinueConversationAsync` to follow the implementation of `BotAdapter`. I also ensure that our override is used even if the object is typecast to `BotAdapter`. `BotAdapter.ContinueConversationAsync` creates a brand new turn context without the underlying compat clients which is not intended. 4. Removed `ICloudAdapter` because it is not needed anymore. `BotAdapter` is an abstract class that allows easy mocking of the CompatAdapter. 5. Without a separate `CompatBotAdapter` DI setup is simplified
…ng for multiple matching routes (#301) - Introduced `ConversationUpdateActivity` and `InstallUpdateActivity` . - Implemented handlers for conversation update (members added/removed, channel created/deleted etc..) and installation update events in `TeamsBot`. - Added support for pattern-based and regex-based message handlers (e.g., responding to "hello" or slash commands like `/help`). - Added TeamsChannelBot, for Channel and Teams related testing - Added warning logs if multiple routes match an activity - Made names for handlers more specific so that warning logs are clear - Added Router to hosting - Removed deserialization methods for teams activities - we never read from json strings - Removed serialization methods for non msg/invoke activities - we only send message activities - Serialization for msg and invoke activities handled centrally be teams activity class - Simplified constructing activities from core activity - Refactored TeamsChannelData to move small channel data specific classes into same file - Fixed duplication of conversation account - Added TODOs for unverified properties/handlers and commented it for now - Moved tests for non msg activities to one file (very few per class) - Made DateTime - > string
This pull request introduces several improvements and refactorings across the Teams bot codebase, focusing on simplifying property management in conversation accounts, enhancing logging for authentication and activity flows, and updating tests for agentic identity support. **TeamsConversationAccount property management:** * Refactored `TeamsConversationAccount` to store all Teams-specific properties in the `Properties` dictionary and provide strongly-typed accessors for each property (e.g., `AadObjectId`, `GivenName`, `Surname`, etc.), simplifying construction and property access. **Logging enhancements:** * Improved logging in `BotAuthenticationHandler` by raising log levels for token acquisition events, and added trace-level logging to output JWT token claims for better debugging. [[1]](diffhunk://#diff-0d237734ffe42c3bd2a77d27777c6ffc86396b9db5cba4f26c22b41918d0384bL35-R40) [[2]](diffhunk://#diff-0d237734ffe42c3bd2a77d27777c6ffc86396b9db5cba4f26c22b41918d0384bR58-R59) [[3]](diffhunk://#diff-0d237734ffe42c3bd2a77d27777c6ffc86396b9db5cba4f26c22b41918d0384bR106-R123) * Enhanced activity sending logs in `ConversationClient` to include the destination URL and improved log message clarity. * Updated startup logs in `BotApplication` to include the listener type for better traceability. **Test and configuration updates:** * Updated unit tests in `TeamsActivityTests` to verify agentic identity properties in the recipient, ensuring correct parsing and assignment. * Added a local settings file to allow specific Bash commands for building and testing in the `core/.claude/settings.local.json`. **Other minor changes:** * Cleaned up configuration code by removing outdated TODO comments about making the MSAL instance configurable. [[1]](diffhunk://#diff-32c43eec964cc43a0cc857afbe1da981ec6000ac6c95c94aef469c4ce859ebe7L213) [[2]](diffhunk://#diff-32c43eec964cc43a0cc857afbe1da981ec6000ac6c95c94aef469c4ce859ebe7L244) [[3]](diffhunk://#diff-32c43eec964cc43a0cc857afbe1da981ec6000ac6c95c94aef469c4ce859ebe7L271) * Fixed logger type in `TeamsBotApplication` constructor for consistency. * Minor formatting improvements in unit tests. * Added missing `using` directive for JWT token handling. * Removed redundant activity logging in `TeamsBotApplication`.
This pull request introduces several improvements and refactorings across the Teams bot codebase, focusing on simplifying property management in conversation accounts, enhancing logging for authentication and activity flows, and updating tests for agentic identity support. **TeamsConversationAccount property management:** * Refactored `TeamsConversationAccount` to store all Teams-specific properties in the `Properties` dictionary and provide strongly-typed accessors for each property (e.g., `AadObjectId`, `GivenName`, `Surname`, etc.), simplifying construction and property access. **Logging enhancements:** * Improved logging in `BotAuthenticationHandler` by raising log levels for token acquisition events, and added trace-level logging to output JWT token claims for better debugging. [[1]](diffhunk://#diff-0d237734ffe42c3bd2a77d27777c6ffc86396b9db5cba4f26c22b41918d0384bL35-R40) [[2]](diffhunk://#diff-0d237734ffe42c3bd2a77d27777c6ffc86396b9db5cba4f26c22b41918d0384bR58-R59) [[3]](diffhunk://#diff-0d237734ffe42c3bd2a77d27777c6ffc86396b9db5cba4f26c22b41918d0384bR106-R123) * Enhanced activity sending logs in `ConversationClient` to include the destination URL and improved log message clarity. * Updated startup logs in `BotApplication` to include the listener type for better traceability. **Test and configuration updates:** * Updated unit tests in `TeamsActivityTests` to verify agentic identity properties in the recipient, ensuring correct parsing and assignment. * Added a local settings file to allow specific Bash commands for building and testing in the `core/.claude/settings.local.json`. **Other minor changes:** * Cleaned up configuration code by removing outdated TODO comments about making the MSAL instance configurable. [[1]](diffhunk://#diff-32c43eec964cc43a0cc857afbe1da981ec6000ac6c95c94aef469c4ce859ebe7L213) [[2]](diffhunk://#diff-32c43eec964cc43a0cc857afbe1da981ec6000ac6c95c94aef469c4ce859ebe7L244) [[3]](diffhunk://#diff-32c43eec964cc43a0cc857afbe1da981ec6000ac6c95c94aef469c4ce859ebe7L271) * Fixed logger type in `TeamsBotApplication` constructor for consistency. * Minor formatting improvements in unit tests. * Added missing `using` directive for JWT token handling. * Removed redundant activity logging in `TeamsBotApplication`.
Expanded logging, builder arg support, improved middleware token
handling, new AddBotApplication overload, and upgraded NuGet packages
for authentication and identity.
This pull request introduces several improvements to the Teams bot
application framework, focusing on enhanced configuration flexibility,
improved dependency management, and minor code cleanups. The most
significant changes include updating method signatures to accept
command-line arguments, refining dependency injection patterns, and
updating package versions for better compatibility and security.
**Configuration and Dependency Injection Enhancements:**
* Changed `TeamsBotApplication.CreateBuilder` and
`TeamsBotApplicationBuilder` constructors to accept a `string[] args`
parameter, allowing applications to pass command-line arguments for more
flexible configuration. (`core/samples/TeamsBot/Program.cs`,
`core/samples/TeamsChannelBot/Program.cs`,
`core/src/Microsoft.Teams.Bot.Apps/TeamsBotApplication.cs`,
`core/src/Microsoft.Teams.Bot.Apps/TeamsBotApplicationBuilder.cs`)
[[1]](diffhunk://#diff-691809f7a90c5bda6ee5e4335c2c393864a32101545fb0b35c24bc659623361bL12-R12)
[[2]](diffhunk://#diff-42051fe23037cc0bf4fa811f899bd3e9cb86edb6178d1ff28bf63ac349db96a9L7-R7)
[[3]](diffhunk://#diff-e196e9ff5fcfc2368d02d38f06cf768e98cf7f8df31c730c799ca33def23a80eL82-R82)
[[4]](diffhunk://#diff-aafa3df8194fb624a2e49d4d9e6065209cbbc17844152cd6fd2e1edfcf7f9fe6L46-R48)
* Added a new `AddBotApplication` extension method to
`IServiceCollection` with a default configuration section name
("AzureAd"), simplifying bot application registration.
(`core/src/Microsoft.Teams.Bot.Core/Hosting/AddBotApplicationExtensions.cs`)
**Dependency Updates:**
* Updated package references in `Microsoft.Teams.Bot.Core.csproj` to
newer versions for `Microsoft.AspNetCore.Authentication.JwtBearer`,
`Microsoft.AspNetCore.Authentication.OpenIdConnect`, and
`Microsoft.Identity.Web` packages, improving compatibility and security.
(`core/src/Microsoft.Teams.Bot.Core/Microsoft.Teams.Bot.Core.csproj`)
**Code Quality and Cleanup:**
* Removed a pending suppress message attribute from the
`TeamsBotApplication` class, cleaning up unnecessary code annotations.
(`core/src/Microsoft.Teams.Bot.Apps/TeamsBotApplication.cs`)
* Updated variable names in the `CompatAdapter` to improve clarity and
consistency, and ensured cancellation tokens are propagated correctly.
(`core/src/Microsoft.Teams.Bot.Compat/CompatAdapter.cs`)
**Minor Configuration Update:**
* Changed logging configuration in `appsettings.json` to trace logs for
`Microsoft.Teams` instead of `Microsoft.Bot`, aligning logging with the
Teams bot framework. (`core/samples/CoreBot/appsettings.json`)
Seems our CI is broken because of dotnet/sdk#53006 I use this opportunity to consolidate SuppressError messages. This pull request refactors how code analysis suppressions are managed across the solution. Instead of applying `[SuppressMessage]` attributes directly to classes and methods, project-level suppressions are now centralized in `GlobalSuppressions.cs` files for each relevant project. This change improves maintainability and reduces clutter in the codebase. Key changes include: **Centralization of Code Analysis Suppressions:** * Added new `GlobalSuppressions.cs` files in `Microsoft.Teams.Bot.Core`, `Microsoft.Teams.Bot.Apps`, and `Microsoft.Teams.Bot.Compat` projects to house all project-level suppressions, including rules related to logging performance and design guidelines. [[1]](diffhunk://#diff-a31618c3543ca08086480902914d1b8a2662d91867b152f35a919465c3ac1623R1-R24) [[2]](diffhunk://#diff-46bb45f0e912e49218b1f21c4aa2cdc301655c75a508bc71d8c2e1aa0691c9b4R1-R24) [[3]](diffhunk://#diff-cee1e0aaa0d1fdbef17c0bb1c2b0a64fd3e6680a31c013f8c6b9a70d6fb8ad7bR1-R18) **Removal of Inline SuppressMessage Attributes:** * Removed `[SuppressMessage]` attributes from classes and methods in files such as `Router.cs`, `TeamsApiClient.cs`, `CompatBotAdapter.cs`, `BotApplication.cs`, `ConversationClient.cs`, `JwtExtensions.cs`, `UserTokenClient.cs`, and `BotHttpClient.cs`, as well as from multiple schema/activity/entity classes. These suppressions are now handled at the project level. [[1]](diffhunk://#diff-39661a1e6d086cf06cff19e9627a3424084ccb66df2254a6b56623ef4ccf5016L13-L14) [[2]](diffhunk://#diff-a7b99b48404c7a1f8b81a59f20ace5e826e134eedaeda28dd38a0931db8c4c84L18) [[3]](diffhunk://#diff-c443812ac75b10f0cb9e0929a1165dee72b7c96adbd232d830a65348ccd1b42bL25) [[4]](diffhunk://#diff-2c89073290ce62fb61faed0da2a6153c8e93b318a57364fdbf4c3da6e440a436L16) [[5]](diffhunk://#diff-d62a8ce4aac677906758eb430b84c9432f61ff95342701fdcae909310e2aed27L18) [[6]](diffhunk://#diff-d3d44d1fb1f7c0af05be370ba32f80e12a136f7876e896ecf1a9facf97655c70L22) [[7]](diffhunk://#diff-1943bfd92d68530022946c449fa60ec24a9032e9ad2bee4978ae0dc59bdc1739L24) [[8]](diffhunk://#diff-44232a3c089c8de3dc8fdc228feebdda822293f4be104d00e28275525c46c8c2L19) [[9]](diffhunk://#diff-44232a3c089c8de3dc8fdc228feebdda822293f4be104d00e28275525c46c8c2L38) [[10]](diffhunk://#diff-44232a3c089c8de3dc8fdc228feebdda822293f4be104d00e28275525c46c8c2L70) [[11]](diffhunk://#diff-44232a3c089c8de3dc8fdc228feebdda822293f4be104d00e28275525c46c8c2L101) [[12]](diffhunk://#diff-44232a3c089c8de3dc8fdc228feebdda822293f4be104d00e28275525c46c8c2L124) [[13]](diffhunk://#diff-b9fe8c2661f373312865c34021dcd68b97c7a7308d3814767e941a9e275212f4L13) [[14]](diffhunk://#diff-f1c9ac72f51f1e74cdd25fd72f5b26a7ef64c41e998340dc92bf0c3501e4ee50L13) [[15]](diffhunk://#diff-c012032b5d678f0c2c0adc3b209525719f308955fd766238e6f64ec324ca2c45L14) [[16]](diffhunk://#diff-8fea9343e8aa50c65ec8c4a88b2040380b0b27da68735c7474bda5e7379e7456L11) **Addition of New Suppression Rules:** * Introduced a new suppression for `CA1054:URI-like parameters should not be strings` in the `Microsoft.Teams.Bot.Core.Http` namespace, with justification for consistency with existing API patterns. These changes collectively make code analysis suppression more scalable and easier to manage as the codebase evolves.
- Create Router internally with dedicated logger instead of injecting as dependency --------- Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
* Added all invoke activities ( some are commented that could not be tested ) * Added `AllInvokesBot` sample project for adaptive card actions, task modules, file consent, and other invoke scenarios. * Added `MessageExtensionBot` sample project. * Made invoke activity and invoke response strongly typed vi generics.
- Refactored `CompatAdapter` to take in the required objects instead of the service provider object, and then resolving them through it. - Introduce `KeyedBotAuthenticationHandler` which configures auth based on keyed configurations. Add MSAL configurations under a key, and use that the instantiate this object and viola! - Update incomming token validation to be based on keyed configurations as well. - As a consequence of the above changes, it is possible multiple keyed instances of `TeamsBotApplication` and `CompatAdapter` allowing for multiples apps to be hosted in a single process. - Introduce PABot and CompatProactive samples, that test out PA scenarios and proactive messaging scenarios, respectively. **Testing** - [x] PABot setup working - [x] PABot EchoBot working - [ ] PABot TeamsBot working - [ ] CompatProactive working - [x] Integration with PA codebase working --------- Co-authored-by: Kavin Singh <kavinsingh@microsoft.com>
**Core SDK Enhancements:** * Introduced `EventActivity` and `EventActivity<TValue>` classes to represent event activities, including strongly-typed value payloads. Also added `EventNames` constants for meeting event types. * Defined strongly-typed value classes for meeting events: `MeetingStartValue`, `MeetingEndValue`, `MeetingParticipantJoinValue`, and `MeetingParticipantLeaveValue`, as well as related participant info classes. * Added `MeetingHandler.cs` with extension methods for registering handlers for meeting start, end, participant join, and participant leave events in `TeamsBotApplication`. **Sample Bot and Documentation:** * Added a new sample bot, `MeetingsBot`, including its project file, implementation (`Program.cs`), configuration (`appsettings.json`), and a detailed README explaining manifest requirements and Teams setup for meeting events. * Updated the solution file `core.slnx` to include the new `MeetingsBot` sample.
Introduced ReplyToId property in CoreActivity and builder, enabling reply tracking in activities. Updated ConversationClient to append ReplyToId to outgoing URLs and adjusted "agents" channel ID truncation. Simplified bot setup in Program.cs by removing telemetry and generic parameters. Added a default route overload for UseBotApplication. Minor logging and comment improvements. This pull request introduces improvements to how reply handling is managed in the bot framework, particularly around supporting and propagating the `ReplyToId` property in activities. The changes ensure that reply chains are correctly maintained and that conversation IDs are truncated to the correct length for the 'agents' channel. Additionally, the API for registering the bot application has been streamlined. **Reply handling and activity schema improvements:** * Added a `ReplyToId` property to the `CoreActivity` class, enabling activities to specify which message they are replying to. * Updated `CoreActivityBuilder` to set `ReplyToId` when copying from another activity and added a `WithReplyToId` method for explicit setting. [[1]](diffhunk://#diff-5e00975e375bcb87e6b0d28d2367d865865a1254f089cfcab0d6abbb5db4be38R52-R56) [[2]](diffhunk://#diff-5e00975e375bcb87e6b0d28d2367d865865a1254f089cfcab0d6abbb5db4be38R86-R96) **Message sending and routing improvements:** * Modified `SendActivityAsync` in `ConversationClient` to append `ReplyToId` to the outgoing message URL if present, ensuring replies are correctly threaded. Also, fixed conversation ID truncation for the 'agents' channel to a maximum of 100 characters (was 325). * Added a new overload of `UseBotApplication` to simplify bot application setup with a default route. **Sample and registration cleanup:** * Updated the sample bot (`CoreBot/Program.cs`) to use the new `AddBotApplication` and `UseBotApplication` APIs, and cleaned up reply message formatting.
## Summary - Decoupling `IConfiguration` from the `TeamsBotApplication` and `BotApplication` classes since it's not clear what configurations are required. ## Test plan - [x] Verify bot starts and logs the correct AppID at startup - [x] Test with each config format: `MicrosoftAppId`, `CLIENT_ID`, and `AzureAd:ClientId` - [x] Confirm `BotApplicationOptions.AppId` defaults to empty string when no config key is present --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
When setting up components manually BotApplicationOptions is probably the least important argument. So it makes sense to make it optional. --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces the foundational structure for the new
Microsoft.Bot.Corelibrary, establishing core activity and schema types, build configuration, and initial unit tests. The changes set up the basic serialization/deserialization logic for bot activities, extensibility for custom properties, and the CI workflow for automated builds and tests.Core Library and Schema Implementation:
CoreActivityclass and supporting schema types (ActivityTypes,ChannelData,Conversation,ConversationAccount, and extensibility for additional properties) in theMicrosoft.Bot.Core.Schemanamespace, including JSON serialization/deserialization logic and reply creation methods. [1] [2] [3] [4] [5]AddBotApplicationinHostingfor future extensibility.Build and Solution Configuration:
core.slnxsolution file referencing the main project, unit test project, and solution items for centralized configuration.Directory.Build.propsandDirectory.Build.targets, including code analysis, documentation, and versioning with Nerdbank.GitVersioning. [1] [2]Microsoft.Bot.Core.csproj) to target both .NET 8 and .NET 10, with appropriate package references for authentication and identity.Continuous Integration:
core-ci.yaml) for building and testing the core library on push and pull requests to thenext/corebranch.Unit Testing:
Microsoft.Bot.Core.UnitTests) with dependencies on xUnit and coverlet for code coverage, and a test suite validating extensibility and serialization/deserialization of custom activity types. [1] [2]Add .NET solution for extensible bot activity schemas with modern serialization, extension data, and reply support. Includes CI workflow, semantic versioning, and comprehensive unit tests for schema evolution and custom fields.