packager | project contains some scripts that run some basic tests | Build Tool library

You have net6.0 target framework which is still not released while you have installed EF6 which is a previous iteration Entity Framework (mainly used with legacy .NET Framework projects) and you also have EF Core (a modern iteration of it) but older version - 5.0 (which you are actually using for your context, see the using Microsoft.EntityFrameworkCore; statements there).

Try removing EntityFramework package and installing preview version of Microsoft.EntityFrameworkCore.SqlServer (possibly just updating to the latest 5 version also can help) and either removing completely or installing preview version of Microsoft.EntityFrameworkCore.Design. (Also I would recommend to update your SDK to rc and install rc versions of packages).

Or try removing the reference to EntityFramework (not Core one) and changing target framework to net5.0 (if you have it installed on your machine).

As for why do you see this exception - I would guess it is related to new methods added to Queryable in .NET 6 which made one of this checks to fail.

TL;DR

As mentioned in the comments - update EF Core to the corresponding latest version (worked for 5.0 and 3.1) or update to .NET 6.0 and EF Core 6.

The .net standard you are using 2.1 but ,Microsoft.Azure.Functions.Extensions can be support upto .NET Standard 2.0

You should add the below package to your function app and deploy to Azure again.

I came across the same issue trying to scaffold an existing MySQL database. It looks like the latest version of MySql.EntityFrameworkCore (6.0.0-preview3.1) still uses the EFCore 5.0 libraries and has not been updated to EFCore 6.0.

It also seems Microsoft.EntityFrameworkCore.Diagnostics was last implemented in EFCore 5 and removed in 6.

When I downgraded all the packages to the 5 version level, I was able to run the scaffold command without that error.

Without showing actual code and giving a more descriptive detailing about what's going on aside from "it doesn't work" it's difficult to say exactly what is occurring here but I'll do my best.

Thankfully, according to Microsoft's documentation you most certainly can run the Powershell SDK in a self-contained .Net application.

A self-contained .NET application can use Microsoft.PowerShell.SDK to run arbitrary PowerShell functionality without depending on any external PowerShell installations or libraries.

This leads me to believe that you may not be having an issue with the SDK itself but rather with the compiler.

Single-File deployments

I noticed in your screenshot that you are attempting to perform a single-file deployment. You could potentially be having a few issues here. One is to ensure that you're not using an incompatible API. If you are calling any of these within your application, that could be a factor:

• Assembly.CodeBase
• Assembly.EscapedCodeBase
• Assembly.GetFile
• Assembly.GetFiles
• Assembly.Location
• AssemblyName.CodeBase
• AssemblyName.EscapedCodeBase
• Module.FullyQualifiedName
• Module.Name

As none of these are compatible with single-file deployments.

Trimming

Another issue you may be experiencing is referred to as trimming. This is where the compiler will 'trim' unused assemblies from the project at compile time and tends to happen on release runs. While I believe this is off by default you can add the following to your .csproj file to ensure that trimming is disabled:

Yes, that works. Just use a variable for the versions.

Like so:

In my case, it was the SDK not running the proper net6.0 version.

While the whole project was using new net6.0 NuGet packages, the local SDK on that one machine I was working on was still net5.0. After installing .net6.0, Swashbuckle 6.2.3 was working again, and all was as expected.

The issue turned out to be the culture on the NuGet package itself.

The culture on the NuGet package was set to "en-US", while the culture on the consuming assembly was set to neutral (""). This prevented the consuming assembly from being able to load the NuGet package's assembly at runtime.

The solution was to set the culture on the NuGet package to neutral (""), republish the package, and update the package reference in the consuming assembly.

(Thanks to Hamlet Hakobyan for pointing me in the right direction.)

You have two choices:

1. use DateTime instead of DateOnly.

2. build a custom converter (see below).

As far I can see, the actual version of Entity Framework Core issue tracker states that model builder does not support it (find the issue here). Building a converter may solve your issue (cited from there):

Looks like somehow IntelliSense was confused by the other overload. Indeed IServiceCollection does NOT have Configuration property, but HostBuilderContext does.

ConfigureServices has another overload that expose both parameters. This fixes the problem: