Ionide-vscode-fsharp: "Project parsing failed" always there

[vbfox]

The vast majority of our projects can't be parsed because they use advanced msbuild concept and the project-cracker parser can't work on them. That's ok I don't care we don't use ionide as our main editor on theses, they require an editor that is aware of C#/F# cross-language solutions anyway (Even VS is barely there).

1. It's now showing ~70 notifications each time I open the folder/solution in VS code (could be acceptable even if very annoying, one notification for the solution would be largely enough)
   
2. Each time I switch files to one that is in such projects or type in it It show the popup, ALWAYS. I want to review git files changed, check something fast or fix a typo faster that opening the file in VS and this is in my way
   

Suggestions:

• Show startup errors as a bundle per-solution/folder/root of the FSAC loading
• Don't show an error again for a project unless the project file itself changed
• Maybe Optionally disable the popups via a setting
• Maybe reuse the "Solution" status bar indicator to be solution + Current file project and become red when the project loading failed

(Sorry for the ranty issue, being annoyed by popups 😜)

[Krzysztof-Cieslak]

Yeah, well... I can see how it may be annoying. I’ll add setting since this is easiest fix and then later we will think about potential other improvements

[Krzysztof-Cieslak]

3.24.1 added FSharp.disableFailedProjectNotifications setting

[vbfox]

👍 👍 👍 Thanks, you're the best, just beware that fixing bugs / releasing so fast you might enter @forki territory :)

[tonyx]

I have the same problem here. It looks like it started after I opened the project with Xamarin and updated the packages from there.

[matthid]

Also the notifications go crasy when running paket integration tests for example (as it copies fsproj/csproj files back and forth). So it might be resonable to allow ignoring some directories?

[SteveGilham]

Applying FSharp.disableFailedProjectNotifications and restarting VSCode has reduced, but not entirely eliminated this issue for me; there is nothing that stands out as to why two of my projects still show parse failures, yet others with similar customizations do not.

[SteveGilham]

Hmm. Returning after a break, and checking the status (i.e. clicking the "Show status" button) of those two projects finally yielded up a success, with a remark about dependencies having been restored, which may have been the "why those two" at that precise moment in time.

[SteveGilham]

I think I've tracked down what is making this happen -- when a build is running (a FAKE script launched from a separate console) and its starts compiling the affected projects, that is the point where the Project parsing failed: messages arise.

As noted, this is with FSharp.disableFailedProjectNotifications (a flag whose existence I discovered only from this issue) already applied.

[rojepp]

What are the 'advanced concepts' that don't work? Ionide has been like this for a few months for me now, even for really simple projects.

[Krzysztof-Cieslak]

I've added the Disable notification button to the error message in the https://github.com/ionide/ionide-vscode-fsharp/commit/84919bd93a3c49985d14e0e8f235944047b63809. This should fix the discoverability issue for the option turning off notifications