Entityframework.docs: Show an example for .Net Core other than ASP.Net Core

[RowlandShaw]

There are examples for .Net Classic which is app.config happy, and ASP.Net core which talks about appsettings.json as a ASP.Net Core configuration system, but the case for .net Core console apps is plain absent (nor any pointer to a relevant place to look, for those migrating from the classic platforms...)

---

Document details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: de9db02d-7310-1141-6aeb-539c02326a36
• Version Independent ID: 90062036-aa01-3f73-dac9-b4a092245721
• Content: Connection Strings - EF Core
• Content Source: entity-framework/core/miscellaneous/connection-strings.md
• Product: entity-framework
• GitHub Login: @rowanmiller
• Microsoft Alias: divega

[dyslexicanaboko]

I feel your pain: https://blog.bitscry.com/2017/05/30/appsettings-json-in-net-core-console-app/

[bigtfromaz]

Ditto

[divega]

@RowlandShaw @dyslexicanaboko @bigtfromaz there is an example that is a .NET Core console app at https://docs.microsoft.com/ef/core/get-started/netcore/new-db-sqlite. Wondering if your feedback is about the fact that you were not able to find it, that you would like to see examples of what to do with configuration (e.g. connection strings) in console apps, or something else.

[bigtfromaz]

I am looking for best practice when a .Net Standard library needs it's own runtime configuration, no matter where it is being used. In my case the business rules layer of the app is entirely encased in a std library. It is the only library that is to access the database. However each UI app that consumes the library needs to supply configuration values. app.config was a way to do that.

[RowlandShaw]

I was thinking more the what to do with the configuration, having come from EF6 that happily goes looking for the DefaultConnection in the app.config's configuration settings without having to think about it

[spivonious]

@bigtfromaz - I think best practice would be to pass in any needed configuration as parameters and not rely on app.config/appsettings.json.

[roji]

@divega it seems that a small sample for a .NET Core console application with a Microsoft.Extensions.Configuration could make sense, as well as a small note on why hard-coding the connection string is unadvisable. Note also #1344 which seems to be a dup of this.

[roji]

There seem to be other requests on the same page for other types of connection strings (e.g. non-LocalDB, Azure...). As brief section pointing users to the right pages could help.

[divega]

@roji from what I am reading in the comments from @bigtfromaz and @RowlandShaw, this issue was motivated by how the new configuration system doesn’t have a global static entry point that you can access from everywhere, but you rather need to pass around an IConfiguration directly or via de DI container. I.e. the main scenario mentioned is how to flow the application’s connection string into a .NET Standard library.

This is a concern that has been raised before, and it is product of a conscious design trade off.

It is actually a bit orthogonal to EF Core, but a sample of how to flow the connection string using EF Core or Microsoft.Configuration.Extensions abstractions would probably help.

I agree that having a page linking to the right way to configure for different data sources would help. The place for this kind of thing already exists in the providers page, but perhaps things can be improved. We currently link to the docs of the providers, but in many cases it is just a readme file that doesn't contain this kind of information.

[ajcvickers]

Dupe of #481