fsprojects / fsprojects/FSharp.Data.SqlClient
Must System.Configuration.ConfigurationManager be manually installed?
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 206
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Description
In a netstandard2.0 project I have this:
new SqlCommandProvider<const(SqlFile<"myfile.sql">.Text), "name=MyConnStr">()
When I run the app (ASP.NET Core targeting net472) and make a DB query, I get an exception saying "Could not load file or assembly 'System.Configuration.ConfigurationManager`.
The problem goes away if I manually install the System.Configuration.ConfigurationManager NuGet package, or if I use a complete connection string instead of name=MyConnStr.
Is manual installation of System.Configuration.ConfigurationManager required, or is this an issue with SqlClient? Perhaps it's related to https://github.com/fsprojects/FSharp.Data.SqlClient/issues/349#issuecomment-536443977?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the SqlCommandProvider connection-name path used by name=MyConnStr, and compare it with the complete connection-string path. Review the related issue comment and the package dependency behavior for an ASP.NET Core app targeting net472. Done means establishing whether System.Configuration.ConfigurationManager must be installed manually and documenting or correcting the dependency behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100