Merge pull request #5372 from dotnet/main

Auto Publish – main to live - 2026-06-01 23:01 UTC

Author: learn-build-service-prod[bot]

entity-framework/core/managing-schemas/scaffolding/index.md

@@ -136,6 +136,8 @@ Scaffold-DbContext ... -Tables Customer.Purchases, Contractor.Accounts, Contract
 
 Table and column names are fixed up to better match the .NET naming conventions for types and properties by default. Specifying `-UseDatabaseNames` (Visual Studio PMC) or `--use-database-names` (.NET CLI) will disable this behavior preserving the original database names as much as possible. Invalid .NET identifiers will still be fixed and synthesized names like navigation properties will still conform to .NET naming conventions.
 
+To disable the pluralizer when scaffolding reverse-engineered models, use `-NoPluralize` (Visual Studio PMC) or `--no-pluralize` (.NET CLI).
+
 For example, consider the following tables:
 
 ```sql

entity-framework/core/modeling/index.md

@@ -42,6 +42,9 @@ It is possible to apply all configuration specified in types implementing `IEnti
 > [!NOTE]
 > The order in which the configurations will be applied is undefined, therefore this method should only be used when the order doesn't matter.
 
+> [!NOTE]
+> `ApplyConfigurationsFromAssembly` only instantiates configuration types that have a parameterless constructor; the constructor may be public or non-public. Types whose constructors require parameters are skipped, and a `SkippedEntityTypeConfigurationWarning` is logged. To apply such configurations, instantiate them manually and pass them to <xref:Microsoft.EntityFrameworkCore.ModelBuilder.ApplyConfiguration%2A>.
+
 #### Using `EntityTypeConfigurationAttribute` on entity types
 
 Rather than explicitly calling `Configure`, an <xref:Microsoft.EntityFrameworkCore.EntityTypeConfigurationAttribute> can instead be placed on the entity type such that EF Core can find and use appropriate configuration. For example: