Problems creating more schemas in PostgreSQL + .NET Core - entity-framework

Question

We recently created a web project in .NET Core and are using PostgreSQL via NPGSQL Entity Framework extension. At first, there were no problems at all. But when trying to add more schemas, the new schema was not created. According to other posts on the Internet, we should not be limited to any number of schemas. Does anybody know what might cause the problem?
P.S.: After dropping the original schema, the new schema was successfully created. However, trying to add next schema without dropping the previous one seems like a problem.
FooDbContext.cs
public class FooDbContext : DbContext
{
/// <summary>
/// For unit testing.
/// </summary>
public FooDbContext()
: base()
{
}
public FooDbContext(DbContextOptions<FooDbContext> options)
: base(options)
{
}
public virtual DbSet<Person> People { get; set; }
public virtual DbSet<Project> Projects { get; set; }
public virtual DbSet<PersonOnProject> PeopleOnProjects { get; set; }
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
modelBuilder.HasDefaultSchema("TestingFoo");
base.OnModelCreating(modelBuilder);
}
}
Startup.cs
...
public void ConfigureServices(IServiceCollection services)
{
// Add framework services.
services.AddEntityFrameworkNpgsql().AddDbContext<Model.FooDbContext>((provider, builder) => {
builder.UseNpgsql(Configuration.GetConnectionString("LocalDb"), b => b.MigrationsAssembly("TestingFoo"));
});
services.AddMvc();
}
....
public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
{
loggerFactory.AddConsole(Configuration.GetSection("Logging"));
loggerFactory.AddDebug();
app.ApplicationServices.GetService<Model.FooDbContext>().Database.EnsureCreated();
app.Use(async (context, next) =>
{
await next();
if (context.Response.StatusCode == 404
&& !Path.HasExtension(context.Request.Path.Value))
{
context.Request.Path = "/index.html";
await next();
}
});
app.UseStaticFiles();
app.UseMvc();
}

Answer 1

We found we had difficulty "seeing" other schemas besides "public" until we adjusted the connection string to connect to the cluster instead of the instance.