Add support working with appsettings.json in Asp.Net Core 2.x and above #370

Activity

1. smoothdeveloper commented on Jan 27, 2020

   

   smoothdeveloper

   on Jan 27, 2020

   Collaborator

   More actions

   @rahicks26 is it something you'd like to contribute in a PR?

   I haven't used new ASP.NET stuff.

   To make the changes in the library, one would have to

   • go over the places where NameInConfig is used in the library: https://github.com/fsprojects/FSharp.Data.SqlClient/search?q=NameInConfig&unscoped_q=NameInConfig
   • add a sample project using the new appsettings.json and the provider
   • add unit tests checking the new behaviour
   • not change the behaviour of existing tests using the regular app.config named connection string

   I'd be happy to review and merge such PR.
2. smoothdeveloper

   added

   feature

   on Jan 27, 2020
3. rahicks26 commented on Jan 28, 2020

   

   rahicks26

   on Jan 28, 2020

   Author

   More actions

   @smoothdeveloper yeah that sounds fun. I will take a look this weekend and see what I can make of it.
4. github-actions commented on Mar 14, 2026

   

   github-actionsBot

   on Mar 14, 2026 – with GitHub Actions

   Contributor

   More actions

   🤖 This is an automated response from Repo Assist.

   Good news — I've opened a draft PR that adds appsettings.json support to DesignTimeConnectionString: this run's PR (see the Monthly Activity issue #449 for the link once it's created).

   What the PR does:

   • When no app.config or web.config is found, ReadFromConfig now auto-discovers appsettings.json (and appsettings.Development.json) in the resolution folder, reading from the standard ConnectionStrings section:

     {
       "ConnectionStrings": {
         "MyDb": "Server=.;Database=MyApp;Integrated Security=True"
       }
     }

   • You can also pass appsettings.json explicitly as the ConfigFile parameter: ConfigFile = "appsettings.json".
   • The error message when no config file is found now mentions appsettings.json and the ConfigFile parameter.

   Limitation: The runtime connection string lookup still uses System.Configuration.ConfigurationManager, which does not read appsettings.json. So at runtime in ASP.NET Core you should either:

   1. Pass the connection string via the connection constructor parameter (injected from IConfiguration), or
   2. Use a literal connection string at design time (pointing to a dev DB) and inject the production string at runtime.

   This PR unblocks the design-time compilation step that was preventing ASP.NET Core projects from using name=... syntax at all.

   Generated by Repo Assist · ◷

   To install this agentic workflow, run

   gh aw add githubnext/agentics/workflows/repo-assist.md@346204513ecfa08b81566450d7d599556807389f
   
5. github-actions

   added a commit that references this issue on Mar 14, 2026

   feat: add appsettings.json support to DesignTimeConnectionString (Closes

   ...

   This issue will close once commit 617156d is merged into the 'master' branch.

   617156d