ApplyConfigurationsFromAssembly warns about no parameterless constructor for already added DB Configurations

[dstj]

I just upgraded to .NET 9 from .NET 8 and now get a new warning in my logs: "The type '{entityTypeConfig}' was found while scanning assemblies but could not instantiated because it does not have a parameterless constructor."

While I like the concept for error-catching, I get this for UserOAuthAuthorizationDbConfiguration even its configuration is manually added right before the call to ApplyConfigurationsFromAssembly. It requires an encryption utility, so it will never have a parameterless constructor. Consequently, the warning in the log is just noise. ;)

See my OnModelCreating method of my DbContext class:

	protected override void OnModelCreating(ModelBuilder modelBuilder)
	{
		modelBuilder.HasPostgresExtension("uuid-ossp");

		modelBuilder.ApplyConfiguration(new UserOAuthAuthorizationDbConfiguration(this.GetService<IEncryptionUtil>()));
               

		var asm = GetType().Assembly;
		modelBuilder.ApplyConfigurationsFromAssembly(asm, type => modelBuilder.Model.FindEntityType(type) == null);
	}

This seems related to #19691, #32577 and #24748

I believe the ApplyConfigurationsFromAssembly should skip any already loaded configurations.

Include provider and version information

EF Core version: 9.0.0
Database provider: Npgsql.EntityFrameworkCore.PostgreSQL 9.0.2
Target framework: .NET 9
Operating system: Windows 11 Pro
IDE: Jetbrains Rider

[AndriySvyryd]

This is out-of-scope for EF Core. I encourage you to create a copy ApplyConfigurationsFromAssembly and customize it to your needs.

[dstj]

@AndriySvyryd
I'll look at that option, thanks. But I respectfully disagree that avoiding false-positive warnings is out-of-scope. I don't think my use case is so far fetched. Is it???

Can you point out how I would access the list of already registered IEntityTypeConfiguration<> from a copy of ApplyConfigurationsFromAssembly?

Plus, sidenote, trying to copy ApplyConfigurationsFromAssembly forces me to cascade copy SharedTypeExtensions.GetConstructibleTypes and SharedTypeExtensions.GetLoadableDefinedTypes because SharedTypeExtensions is internal.

It, more and more, feels like there should be a simpler way to avoid this warning...