Closed aggieben closed 4 years ago
Check that have you specified FscToolPath in your fsproj-project file? If yes, that should point to a .NET Framework path of fsc.exe compliler , not to .NET Core path of fsc.exe
Try upgrading more recent version of the SQLProvider
@Thorium it appears that I no longer have this issue as of the latest release. Not sure what changed or when it changed. My issue is now https://github.com/fsprojects/SQLProvider/issues/645.
Description
I have failing builds as well as broken intellisense that appears to stem from the following issues:
Apologies for the odd formatting. Here's a screencap if that's easier:![image](https://user-images.githubusercontent.com/1321/64648243-277ab900-d3e0-11e9-8628-38b6c5975dd1.png)
The part of this that has my scratching my head the most is why
FSharp.Core
fails to load.I created this project using forge, but it's just using modified CLI templates for new projects. My
.fsproj
:And my
paket.dependencies
:The versions reported in
paket.lock
for these dependencies are:FSharp.Core
: 4.7Npgsql
: 4.0.9SQLProvider
: 1.1.66I'm using .NET Core 3.0 preview9:
Repro steps
Please provide the steps required to reproduce the problem
Create new project with
forge new
, which creates empty projects with paket already configuredadd SQLProvider, Npgsql, and FSharp.Core to paket.dependencies
paket install
dotnet restore
build or open in ionide-vs
Expected behavior
Type provider works, intellisense works
Actual behavior
Intellisense indicates build problems;
dotnet build
also indicates same top-level errrorsKnown workarounds
Unsure. As best I understand it, recent SDKs (after 2.2?) supposedly don't require the .NET Core type provider workaround. (The issue https://github.com/dotnet/fsharp/issues/3303 is marked obsolete)
Related information
Used database PostgreSQL
Operating system Windows 10
.NET Runtime, CoreCLR or Mono Version: 3.0-preview9