Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Intellisense not working for packages with Ionide in VSCode #421
I am just beginning with FSharp and am trying to work in VSCode on my mac. I've followed all the install instructions here https://github.com/dotnet/netcorecli-fsc/wiki/.NET-Core-SDK-1.0.1
However Inoide can't seem to pick up any of the packages I've added. Here is an example:
As you can see the plugin is running ok as I get type info but it won't pick up the package. Hovering on the red squiggly shows the error
I'm running dotnetcore 1.0.3 and inoide-fsharp 2.25.10
I am experiencing the same issue, and was able to reproduce it with a new project. Here is what I did:
At this point, I see that all Expecto references (the 'open', attributes, etc.) are underlined in red and mousing them shows some variation of "The namespace or module 'Expecto' is not defined."
However, if you run build.cmd, the project builds successfully.
Here are 3 images showing this behavior.
Update to Temp.fsproj: http://imgur.com/OBpLfYK
Build succeeded: http://imgur.com/BJu2tPL
Tests.fs can't recognize the library: http://imgur.com/M601yeA
EDIT: Additional notes:
I followed all 11 steps and cannot reproduce it. I also recreated a project according to @jimmyp 's pic and could not reproduce. Here are the specs I'm using:
(If there are later versions of the ionide packages, they have not appeared for me yet.)
I also tried closing and opening vscode and could not reproduce. I am a bit confused why I cannot reproduce.
@czifro I only have one machine, so difficult to do. I will try to get my hands on another machine and see if I can reproduce there.
EDIT: Here is my setup.
I installed F#, .NET sdks, MSBuild, etc. through the Visual Studio installation tool. I'm not sure if that makes a difference or not.
F# framework is installed in
@czifro I installed F# 4.0 RTM and removed the following line from my Ionide user settings:
I still get the same error, but I also saw something interesting on the
I did not get this same error message when my toolsDirPath was set to 4.1. I changed the log output to "DEBUG" to see if it would provide any more information, but it did not.
If there is a way to get more information about that, please let me know so I can see if that is the root cause of the problem.
I used the developer tools to check further. I saw Ionide requesting a load of the FsProj file and the response was an error.
Here's the request:
I have no idea what this means, though.
Ok, I was able to solve the problem, and here's how I did it.
The key issue I had was that I was receiving an error about Build 14.0 not being available, and the last package solved that.
Installing all this basically gave me .NET Standard 1.x (4?, 5?, ... not sure). The important thing is that it solved my problem.
However, my original code was against .NET 4.6.1 and there were certain functions that the .NET Standard did not contain (or contained with different signatures). I didn't bother trying to install the .NET SDK again. Instead, the problems were few enough and simple enough that I just rewrote those parts of the code.
Hope this helps someone dealing with this problem (at least on Win 7).