Open-source web application framework for ASP.NET Core! Offers an opinionated architecture to build enterprise software solutions with best practices on top of the .NET. Provides the fundamental infrastructure, cross-cutting-concern implementations, startup templates, application modules, UI themes, tooling and documentation.
Is your feature request related to a problem? Please describe the problem.
I'd like to contribute CosmosDB for NoSQL support using the official driver, by implementing the respective EFCore DBContext extensions, similarly to how it's previously had been done for all the SQL databases. So, CosmosDB could be used with the official CosmosDB provider for EF Core.
Describe the solution you'd like
Add a DBContext extension with CosmosDB specific settings, as a subproject Volo.Abp.EntityFrameworkCore.CosmosDB, ensure that CosmosDB is configured and Dependency Injected properly at the root EF Core project.
Additional context
I've seen #2708 #2532 #2310 @hikalkan stated that he moved CosmosDB elsewhere. I've seen #2553 PR as well, but not sure what is the actual CosmosDB status ATM, could use that PR as a basis, although it should be adapted to the fresh project structure.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
I'd like to contribute CosmosDB for NoSQL support using the official driver, by implementing the respective EFCore DBContext extensions, similarly to how it's previously had been done for all the SQL databases. So, CosmosDB could be used with the official CosmosDB provider for EF Core.
Describe the solution you'd like
Add a DBContext extension with CosmosDB specific settings, as a subproject
Volo.Abp.EntityFrameworkCore.CosmosDB
, ensure that CosmosDB is configured and Dependency Injected properly at the root EF Core project.Additional context
I've seen #2708 #2532 #2310 @hikalkan stated that he moved CosmosDB elsewhere. I've seen #2553 PR as well, but not sure what is the actual CosmosDB status ATM, could use that PR as a basis, although it should be adapted to the fresh project structure.