IDE code analysis starts to freeze on large files affecting Intellisense, text coloring, tooltips and responsiveness

[edgarfgp]

While working in Fabulous.Avalonia, had my project in a refactoring "broken" state, and suddenly it went in a borked state . Had to manually remove parts of the code until the IDE was able to handle it again.
Repro steps
Provide the steps required to reproduce the problem:

• Clone https://github.com/fabulous-dev/Fabulous.Avalonia/tree/repro-code-analysis-freeze
• Open Fabulous.Avalonia.sln
• Open Root/State.fs and observe that the code analysis does not finish affecting Intellisense, text coloring, tooltips and responsiveness

If possible, attach a zip file with the repro case. This often makes it easier for others to reproduce.
The zip file should ideally represent the situation just before the call/step that is problematic.

You can find the related IDE snapshot if that help diagnosing the issue https://github.com/fabulous-dev/Fabulous.Avalonia/tree/repro-code-analysis-freeze/idesnapshots

Expected behavior
Regardless of the state of your project. the IDE should be able to analyze/report the state of your code.

Actual behavior
IDE code analysis starts to freeze on large files affecting Intellisense, text coloring, tooltips and responsiveness

Known workarounds
Start removing part of the code in State.fs until the IDE/Compiler is able to handle the solution
Provide a description of any known workarounds.

Related information

Provide any related information (optional):

• Initially reported https://youtrack.jetbrains.com/issue/RIDER-98788/F-code-analysis-freezes-performance-degradation-in-large-files.#focus=Comments-27-8143607.0-0

• Operating system: Window, macOS
• .NET 7.0 (android, iOS)
• Editing Tools: Rider

[vzarytovskii]

This needs an FCS or VS repro, since we're unable to debug rider, and I can't see it in latest VS.

[vzarytovskii]

@auduchinok how old is FCS fork in the affected version?

[0101]

When opening the solution in VS I get:

Output Window says:
Some of the properties associated with the solution could not be read.

But Gallery/Root/State.fs seems to work fine, with coloring, tooltips, completions and hints.

[edgarfgp]

When opening the solution in VS I get:

Output Window says: Some of the properties associated with the solution could not be read.

But Gallery/Root/State.fs seems to work fine, with coloring, tooltips, completions and hints.

Had the same issue and I think is because VS does not support “SingleProject” apart of the Maui one right ? It only works with Rider and that is why difficult for me to have a repro in VS

[vzarytovskii]

When opening the solution in VS I get:

Output Window says: Some of the properties associated with the solution could not be read.

But Gallery/Root/State.fs seems to work fine, with coloring, tooltips, completions and hints.

Had the same issue and I think is because VS does not support “SingleProject” apart of the Maui one right ? It only works with Rider and that is why difficult for me to have a repro in VS

What is SingleProject? We don't explicitly support or restrict it in FSharp.Build.

[edgarfgp]

When opening the solution in VS I get:

Output Window says: Some of the properties associated with the solution could not be read.

But Gallery/Root/State.fs seems to work fine, with coloring, tooltips, completions and hints.

Had the same issue and I think is because VS does not support “SingleProject” apart of the Maui one right ? It only works with Rider and that is why difficult for me to have a repro in VS

What is SingleProject? We don't explicitly support or restrict it in FSharp.Build.

Target multiple platforms from Avalonia single project . Similar to what Maui does it. More info https://learn.microsoft.com/en-us/dotnet/maui/fundamentals/single-project

Update: Basically NET 7 single project with MsBuild custom targets for Mobile,Desktop