fsprojects / fsprojects/FSharp.Data.SqlClient
SqlProgrammabilityProvider design-time: "The given key was not present in the dictionary" and then "No constructors are available" the first time an sproc is used until project reload
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 206
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Description
The first time I use an sproc in code using SqlProgrammabilityProvider, I often get the following error:
The given key was not present in the dictionary

Then after some seconds, it changes to this error:
No constructors are available for the type

This happens even when I get Intellisense autocompletion for the sproc name.
If I remove it and retype it, I only get the second error ("no constructors ...").
The error disappears after project reload (I usually just make an edit to the fsproj and save, and revert and save again to reload the project without losing the open documents).
If it's relevant, my connection strings are
Data Source=.\\SQLEXPRESS;
Initial Catalog=MY_DB_NAME;
Integrated Security=True"
I haven't always gotten the errors, but I seem to consistently get the error for the project I'm working on now.
Unfortunately I don't have a solid repro. Let me know if I can be of further help.
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 by reproducing the first sproc use with SqlProgrammabilityProvider and compare the errors before and after reloading the project. The issue provides no file or test entry point and no solid reproduction; done means the first use no longer produces either error without requiring a project reload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp, sql
- Domain
- databases, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100