How can we use DataServiceContext.CreateQuery Method in .Net Core 3.1 - asp.net-core-3.1

I am migrating code from MVC5 to .Net Core 3.1. I am facing problem with DataServiceContext.CreateQuery Method. What is the alternative of CreateQuery in .Net core 3.1.

Related

Server GRPC core Implementation of GRPC.core in .NET framework 4.8

Samples for grpc.core server implementation in .NET framework 4.7
We are planning to migrate from .NET framework to .NET core (.NET6). As part of this migration, we want to first move to grpc.core from WCF. When we searched for sample service implementation using grpc.core in .NET frameowrk 4.7, we ended up getting nothing. All the results were pointed to the implementation using grpcdotent in dotnet6.
Here is a grpc.core server and client hello world example
This example's server project targets .NET Core 3.1 but you can essentially use the same code/approach for .NET 4.7

How to use EF Core 6.0 with an application that uses .Net Framework?

I have a situation where an application uses various component libraries. The libraries were based on .NetStandard2.0/2.1 and internally used EF Core 3.1. For various deployment and development reasons, we now want to target EF Core 6.0, which raises the following issues.
Net Core 3.1 support runs out in December 2022 so we need to move away from it.
The application uses Net Framework functionality and cannot move to Net Core.
EF Core 6.0 does not support NetStandard, only Net 6.
Changing the library that uses EF Core to target NET 6 means that components referencing it also need to reference Net 6.
Dependencies trickle down to the application that targets Net Framework and, as a result, the application no longer builds because Net Framework is not compatible Net 6.
How can the Net Framework application use the Net 6 assembly? Or, more specifically, how can a Net Framework application use libraries that internally use EF Core 6.0?
The interface between the application (Net Framework) and the one single touch point library component (Netstandard) is very well defined. Maybe Pinvoke could solve the problem? Or something simpler that I have overlooked?
Somewhat related question: NU1202 Package Microsoft.EntityFrameworkCore 6.0.3 is not compatible with netstandard2.1
Other than process to process communication between .NET Framework and .NET 6, this is not supported (for example via a Web API or similar)
As a short term solution, you can change your .Net Standard 2.0 EF Core libraries to be multi targeted to both .Net Standard 2.0 (which will reference EF Core 3.1) and .Net 6 (which will reference EF Core 6). This will let your .Net Core apps use EF Core 6, while allowing your .Net Framework apps to use the same dlls, but to be using EF Core 3.1. I realize that EF Core 3.1 support ends December 2022, but it will keep things moving.
https://learn.microsoft.com/en-us/nuget/create-packages/multiple-target-frameworks-project-file
Btw, has Microsoft even attempted to address the fact that a .Net Framework application cannot reference .Net 6, therefore it cannot use EF Core 6? This is a major issue for us, as we were sold the idea that .Net Standard could be shared between .Net Framework and .Net Core, but this has ceased to be the case since .Net Standard 2.1 was introduced, and now MS has pushed all new features, like EF Core, to .Net 6.

How to work with Subsonic MySQL in ASP.NET Core 3.1?

What are the requirements and how to work with subsonic in ASP.NET Core 3.1 or later versions?
How to build DAL using subsonic in ASP.NET Core 3.1?
What is the use of SubSonic.Core.DAL 4.2.1?

Do I have to use npgsql for a project on prosgresql, EF Core and .net Core

I am starting a project with prosgresql, EF Core and .net Core. For this case is it a must to use npgsql?
It isnt a must to use npgsql you can use EF Core on its own https://www.npgsql.org/efcore/index.html.
However I would recommend using npgsql apposed to EFCORE, I use it for when working with .NET CORE and PostgresSQL they also have great documentation at https://www.npgsql.org/doc/basic-usage.html and you don't need to depend on EF

Can I use Npgsql Data Provider in my .NET 4.0 project?

I have an MVC project that I would like to write in .NET 4.0
Is it possible to use Npgsql (which currently supports .net 3.5 ) if I will use it through Entity Framework, and I will limit myself to features of EF contained within 3.5?
Npgsql now supports .net 4.0 :D so question is no longer valid.