I've published a beta version of Fable 1.2 to be compatible with netcore 2.0. Now I'm making some tests with the Fable template. Fable works, but unfortunately autocompletion doesn't seem to work with Ionide. I noticed if I change the PropertyGroup in the project file to:
<OutputType>Exe</OutputType>
<TargetFramework>netcoreapp2.0</TargetFramework>
and run dotnet restore again, autocompletion works, so maybe the problem affects only library projects and not executable ones? BTW, I see this error in the F# Language Service output when the autocompletion doesn't work:
[11:37:27 DEBUG] RES (049) <- {parse} in 26 ms: Kind={"error"}
Data={"Code":1,"Message":"The file '/Users/alfonsogarciacaronunez/dev/Fable/src/templates/simple/Content/src/App.fs' was not part of the project. Did you call InvalidateConfiguration when the list of files in the project changed?","AdditionalData":{}}
Pinging @enricosada
@alfonsogarciacaro this is being addressed here: https://github.com/fsharp/FSharp.Compiler.Service/issues/792
and then will be addressed in Ionide and everything else using FCS for autocompletion.
Perfect, didn't know about that issue. Thanks @ninjarobot!
Should be fixed in 2.34.0
Working like a charm, thanks a lot for the quick fix to everybody involved!
Hmm, I'm having problems with projects with new SDK (that is, no FSharp.NET.Sdk). Intellisense works at the beginning but if the project gets somewhat complex, it stops after a while. I usually target netstandard2.0 but other users * also reported the same with netstandard1.6 (and new SDK).
When using FSharp.NET.Sdk it usually works, although I had a similar issue in an "old new" project (meaning, new .fsproj using FSharp.NET.Sdk) this morning. In all cases, the error I see in the F# Language Service output is something like:
Data={"FileName":"/Users/alfonsogarciacaronunez/dev/iris/dotnet/src/Frontend/src/Frontend/Frontend.fsproj"}
[12:24:30 ERROR] RES (752) <- {project} ERROR in 67 ms: Error: connect ECONNREFUSED 127.0.0.1:8381 Data=undefined
Is this a known issue? Unfortunately I don't have much time at the moment to make further investigations.
Most helpful comment
Should be fixed in
2.34.0