You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When defining custom Persistence feature, and using sqlserver, There is an error:
`Skip = "Fix efcore setup first ( System.AggregateException : One or more errors occurred. (Services for database providers 'Microsoft.EntityFrameworkCore.SqlServer', 'Microsoft.EntityFrameworkCore.Sqlite' have been registered in the service provider. Only a single database provider can be registered in a service provider. If possible, ensure that Entity Framework is managing its service provider by removing the call to 'UseInternalServiceProvider'. Otherwise, consider conditionally registering the database provider, or maintaining one service provider per database provider.))"
The text was updated successfully, but these errors were encountered:
I haven't seen this before, even when using the SQL Server provider.
The reason the base persistence feature class depends on Sqlite is for convenience for new users, but if it causes issues we should remove that. But it would be good to try and get this issue reproduced first so we can confirm the fix.
Any chance you could produce a simple project that reproduces the issue?
Description
When defining custom Persistence feature, and using sqlserver, There is an error:
`Skip = "Fix efcore setup first ( System.AggregateException : One or more errors occurred. (Services for database providers 'Microsoft.EntityFrameworkCore.SqlServer', 'Microsoft.EntityFrameworkCore.Sqlite' have been registered in the service provider. Only a single database provider can be registered in a service provider. If possible, ensure that Entity Framework is managing its service provider by removing the call to 'UseInternalServiceProvider'. Otherwise, consider conditionally registering the database provider, or maintaining one service provider per database provider.))"
The text was updated successfully, but these errors were encountered: