Volker Milbrandt

We have the same issue with Gradle 7.1 and newer. Therefore we have to stay with Gradle 7.0.2 until this issue is fixed. (Java 11)

Yes, this is one of the Workarounds mentioned. But as far as I understand this requires that from each option group one Argument is selected. At the moment I can't...

The same issue seems to apply on `netstandard2.0` projects using dotnet 2.2.107: Lint failed while analysing project D:\_2\8\s\source\MyProject\MyProject.fsproj. Failed with: error getting msbuild info: internal error, more info returned than...

Would be good to have it fixed on dotnet 2.2.1xx series which is compatible with VisualStudio 2017 (in contract to 2.2.3XX)

I have not investigated how other analysers do the job. But there are some, which do that for other languages, like the [C# analyzer, Rule S125](https://github.com/SonarSource/sonar-dotnet) from SonarQube. Without knowing...

IMHO the issue #364 with `redundantNewKeyword` should be analyzed and fixed for release v1. Neither Steve's required `new` marked redundant nor my `new`no longer marked redundant with upgrading to F#...

At least the [Community SonarQbe F# plugin](https://github.com/jmecsoftware/sonar-fsharp-plugin) is only using FSharpLint and not Fantomas, as it only scans and will not format on it's own. So I'm in great favour...

IMHO following rules should be activated by default: - trailingWhitespaceOnLine - editors can fix this on saving (no whitespaces at line end) and it reduces merge conflicts - maxNumberOfBooleanOperatorsInCondition -...

120 is perfectly fine for me - I know it's controversial and wanted to point out that there are still today reasons (company rules and maintainability, I know that some...

I have the issue, that the message is no longer found when I update from FSharp.Core 4.6.2 to 4.7.0. Code example is unit testing analyzing [this file](https://github.com/jmecsoftware/sonar-fsharp-plugin/blob/master/FsSonarRunner/FsSonarRunnerCore.Test/Resources/LintTestFile.fs). Updating to FSharpLint.Core...