dotnet / dotnet/fsharp

`UnusedOpensAnalyzer` is constantly executed even then disabled causing VS unresponsiveness

Open
#18,762 21 comments 1 reaction 0 assignees View on GitHub
Area-VS-Editor Bug Impact-Medium
Dominant language
F#
Stars
4.3k
Forks
876
Avg merge
4d 11h
Merged PRs (30d)
131

Description

https://developercommunity.visualstudio.com/t/F-UnusedOpensAnalyzer-is-constantly-e/10939016

Looks like `UnusedOpensAnalyzer` constantly crashes and tries to execute again. Which causes Visual Studio to hang up to 30 seconds. **Makes Visual Studio completely unusable!**
Even when `UnusedOpensAnalyzer` is disabled in settings, it is still executed!

Image

**Repro steps**

1. Clone https://github.com/Ecierge/Elmish.Uno/tree/Ecierge
2. Check out `Ecierge` branch
3. Open `Elmish.Uno.sln`
4. Expand `Elmish.Uno` project
5. Open `Binding.fs` or `BindingT.fs`
6. See how `UnusedOpensAnalyzer` constantly appears in logs

**Expected behavior**

1. All code fixes can be disabled if unchecked in VS settings
2. Code fixes do not go into the crash loop

**Actual behavior**

`UnusedOpensAnalyzer` and one more code fix cannot be disabled.
`UnusedOpensAnalyzer` code fix goes into crash loop

**Known workarounds**

Unfortunately, no, and it drastically affects the development productivity

**Related information**

Provide any related information (optional):

* Operating system 10.0.26100.4351
* .NET Core 9.0.302
* FSharp.Core 9.0.202
* Visual Studio Version 17.14.9 Preview 1.0

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.