Closed 0xced closed 2 years ago
/cc @bricelam
Possibly related to the design-time services changes...
Note for triage: cofirmed this still repros with the latest daily build. Does look like it is due to service scoping changes, but haven't been able to pinpoint the issue.
FYI for those impacted by this issue: EF Core 6.0.1 is now available from NuGet.
This is a regression from EF Core 5.
With .NET 5 / EF Core 5
.config/dotnet-tools.json
ef5scaffold.csproj
global.json
Running
dotnet ef dbcontext scaffold --verbose --no-onconfiguring "Server=sqlprosample.database.windows.net;Database=sqlprosample;User=sqlproro;Password=nh{Zd?*8ZU@Y}Bb#" Microsoft.EntityFrameworkCore.SqlServer
prints many verbose logs. This is the expected behaviour.With .NET 6 / EF Core 6
.config/dotnet-tools.json
ef6scaffold.csproj
global.json
Running the same command
dotnet ef dbcontext scaffold --verbose --no-onconfiguring "Server=sqlprosample.database.windows.net;Database=sqlprosample;User=sqlproro;Password=nh{Zd?*8ZU@Y}Bb#" Microsoft.EntityFrameworkCore.SqlServer
does not print verbose logs anymore. Here is the full output:All the Found default schema, Found table, Found column with table, Found primary key with name are not printed anymore at all.
Also, scaffolding on this particular database should produce warnings (see #25729 and #25748) but they are not printed at all, regardless of the
--verbose
option. It looks like the many different logging/diagnostics/reporter components at play during scaffolding are not properly hooked together.