Ionide-vscode-fsharp: FSX files full of errors since 4.1.0

[ronaldschlenker]

Since I updated to 4.1.0, I get a lot of error messages in fsx files.

• It seems that even basic types like string and int cause an error message, as you can see in the attached screenshot.
• When I move back to 4.0.6, it's ok again - no error messages.
• There are a lot more "Code: -32603" error messages in the log (also on the screenshot) - may be related to #1182.

Bug may be related to #1215, but since the described behavior definitely came with 4.1.0 (some hours ago), it's propably another issue.

[open-collective-bot[bot]]

Hey @ronaldschlenker :wave:,

Thank you for opening an issue. We will get back to you as
soon as we can. Also, check out our OpenCollective and consider
backing us.

https://opencollective.com/ionide

PS.: We offer backer support for all backers. Don't forget to add backer label when you start backing us :smile:

[dlidstrom]

Yep I am seeing this as well. Not only fsx files though, regular fs files as well.

[baronfel]

Can either of you see if you might be hitting https://github.com/fsharp/FsAutoComplete/issues/457? Essentially I'm wondering if you have mixed file soearator slashes in your project files. If you have the verbose logging on, you can verify this by seeing if the Files property of the 'fsharp/notifyWorkspace' even is an empty array.

[dlidstrom]

I have a small project file, just this:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net472</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <Compile Include="Srtp.fs" />
    <Compile Include="Program.fs" />
  </ItemGroup>
  <Import Project="..\fsc.props" />
  <Import Project="..\.paket\Paket.Restore.targets" />
</Project>

[MangelMaxime]

In general, I start my .fsx files with:

#if !FAKE
#r "Facades/netstandard"
#r "netstandard"

It required 1-2 years ago. I am not sure if it still the case or no.

[ollipekka]

git clean -xdf and good old medicine 'Reload window' sorted this for me which seems strange.

[isaacabraham]

I've temporarily fixed this by reverting FSAC to netframework instead of netcore in settings.

[Krzysztof-Cieslak]

Should be fixed in 4.2.0

[lfr]

I still have the problem with 4.2.0, but @isaacabraham's workaround works for me

[almostSouji]

I can also still reproduce this with 4.2.0 changing FSAC to net does indeed work

[davidspiess]

I still have this problem with 4.9.0 on MacOS Catalina, switched to net too.

[nrolland]

FWIW I had that pb with some preview versions, uninstalling them with uninstall tools fixed it
```
$ dotnet --info
..
Host (useful for support):
Version: 5.0.0-preview.4.20251.6
Commit: 47ec733ba7

after uninstall

 ```
$ dotnet --info              
.NET Core SDK (reflecting any global.json):
 Version:   3.1.300
 Commit:    b2475c1295

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.13
 OS Platform: Darwin
 RID:         osx.10.13-x64
 Base Path:   /usr/local/share/dotnet/sdk/3.1.300/

Host (useful for support):
  Version: 3.1.4
  Commit:  0c2e69caa6

[ErikSchierboom]

I'm using the .NET 5 SDK and had the same issue. Reverting back to the .NET backend fixes it.