[Feature] SQLite support for NetStandard 2.0
SteveBush opened this issue · 1 comments
Is your feature request related to a problem? Please describe.
I plan to use the Sqlite Inbox and Outbox in a NetFramework 4.62 project which only supports NetStandard 2.0. All of the SQLite Brighter projects are compatible with NetStandard 2.0 except for the Paramore.Brighter.Sqlite.EntityFrameworkCore project (requires NetStandard 2.1) due to its dependency on Microsoft.EntityFrameworkCore.
Describe the solution you'd like
The following projects use a TargetFramework of NetStandard 2.0 vs 2.1:
- src\Paramore.Brighter.Inbox.Sqlite\Paramore.Brighter.Inbox.Sqlite.csproj
- src\Paramore.Brighter.Outbox.Sqlite\Paramore.Brighter.Outbox.Sqlite.csproj
- src\Paramore.Brighter.Sqlite.Dapper\Paramore.Brighter.Sqlite.Dapper.csproj
- src\Paramore.Brighter.Sqlite\Paramore.Brighter.Sqlite.csproj
No changes to Paramore.Brighter.Sqlite.EntityFrameworkCore (stays on NetStandard2.1 due to dependency on Microsoft.EntityFrameworkCore/
Describe alternatives you've considered
I have built and tested the change.
Additional context
Changes to NetStandard 2.0 would enable a broader set of consumers.
I updated my PR to just add NetStandard2.0 support rather than replace NetStandard2.1 support. NetStandard2.0 doesn't support some asynchronous APIs with cancellation support. I added code to make these instances synchronous without cancellation support on NetStandard2.0.