Add IMongoClient constructor support to MongoDbContext for .NET Aspire integration #104
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 PR adds support for initializing
MongoDbContextdirectly from anIMongoClientinstance, enabling seamless integration with .NET Aspire's MongoDB integration whereIMongoClientis already registered in the dependency injection container.Problem
When using .NET Aspire with MongoDB, the
Aspire.MongoDB.Driver.v3package registers anIMongoClientin the DI container. However, the existingMongoDbContextonly provided constructors that acceptMongoOptions, making it difficult to leverage the pre-configured client without workarounds.Solution
Added new constructor overloads to
MongoDbContext:Usage Example
Implementation Details
MongoDatabaseBuilderto support bothMongoOptionsandIMongoClientinitializationIMongoDbContextinterfaceIMongoClientTesting
Benefits
IMongoClientfor unit testsFixes #103.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.