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
In the last year, Mongo has released a MongoDB EF Core Provider. EF Core is the preferred data access library for ASP.NET Core. SIL.DataAccess was necessary, because there was no EF Core provider for MongoDB. Now that there is, it would probably be worth investigating replacing SIL.DataAccess altogether.
The text was updated successfully, but these errors were encountered:
It appears that there are significant limitations to EF core right now, including not being able to use Select(). I see no drawback in holding off for right now until 1 or 2 more versions come out.
As per conversation with Damien, although we are using Select(), we are using it after we already grab the data from the database. There are no perceived issues with migrating to EF Core.
In the last year, Mongo has released a MongoDB EF Core Provider. EF Core is the preferred data access library for ASP.NET Core. SIL.DataAccess was necessary, because there was no EF Core provider for MongoDB. Now that there is, it would probably be worth investigating replacing SIL.DataAccess altogether.
The text was updated successfully, but these errors were encountered: