David Fowler
David Fowler
@danegsta This can't be just dev mode, what's happens when you publish/deploy?
I’m guessing we have a general problem with bind mounts when docker is running via WSL.
We can consider this a future runtime combo to support, but not right now. We should document this in the mean time.
I originally did this but it breaks applications that were using the `CreateWebHost` pattern, that's why it got moved to be a fallback. I can think of a sneaky way...
I wonder if we can make a small change here to make the TestServer property be null if it a real server is in use. Instead typing the server [here](https://github.com/dotnet/aspnetcore/blob/90c3c97c8d7a16e87bd851de3ec92b3ed3fa954f/src/Mvc/Mvc.Testing/src/WebApplicationFactory.cs#L205)...
> Not blocking, but for futureproofing also change EnrichNpgsqlDbContext, EnrichMySqlDbContext, EnrichOracleDatabaseDbContext and EnrichCosmosDbContext to use ConfigureDbContext We want to use these new APIs as part of these EF upgrade so...
backport this to rc1 please
cc @maddymontaquila @JamesNK @adamint
This is in 9.5. @JamesNK are you going to close this issue?
There's a misunderstanding. PublishAsDockerComposeService is to modify the compose service definition. By default all containers will become docker compose services. If you want to use an external redis at publish...