Setting to generate context with one single constructor for pooling [FEATURE REQUEST]

EF Core supports context poling by calling AddDbContextPool<>() instead of AddDbContext<>() inside ConfigureServices() method. But this requires context to have only one single constructor with options parameter:

InvalidOperationException: The DbContext of type 'DataContext' cannot be pooled because it does not have a single public constructor accepting a single parameter of type DbContextOptions.

To workaround this I commented the following lines in local copy of EFCoreDesigner.ttinclude file:

// Output("/// <inheritdoc />"); // Output($"public {modelRoot.EntityContainerName}() : base()"); // Output("{"); // Output("}"); // NL();

It would be great to add setting for that in Entity Context section of diagram properties 😃

[rlarik]

something nags at me that I put that there for a reason but, of course, didn’t document it at the time so don’t remember why now

Generating a migration without a parameterless constructor results in an error: Unable to create an object of type ‘DataContext’. For the different patterns supported at design time, see https://go.microsoft.com/fwlink/?linkid=851728

Adding the empty constructor back fixes this problem. Where in the docs have you added the information?

[msawczyn]

Now that you mention it, neither do I. I’m removing that. If anyone wants it back, it can be added to their partial. I’ll put something in the docs about that - something nags at me that I put that there for a reason but, of course, didn’t document it at the time so don’t remember why now. (https://i.redd.it/hwqj7yx9vm211.jpg)