You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's very strange for me to disallow setting "warning" or "error" severity for some rules because of performance. Developers can disable rules in case of performance issues. For example, recently we found out that IDE0005 takes about 11-14 minutes (out of 18 minutes for all analyzers) of build time in our solution. And we successfully disabled only this rule.
Maybe it's better to change all EnforceOnBuild.Never to EnforceOnBuild.WhenExplicitlyEnabled?
Brief description:
Developers cannot enable enforce on build for some IDE rules. In my case it's IDE0001 and IDE0049.
I found related TODO in code: https://github.com/dotnet/roslyn/blob/main/src/Analyzers/Core/Analyzers/EnforceOnBuildValues.cs#L134.
It's very strange for me to disallow setting "warning" or "error" severity for some rules because of performance. Developers can disable rules in case of performance issues. For example, recently we found out that IDE0005 takes about 11-14 minutes (out of 18 minutes for all analyzers) of build time in our solution. And we successfully disabled only this rule.
Maybe it's better to change all
EnforceOnBuild.Never
toEnforceOnBuild.WhenExplicitlyEnabled
?cc: @mavasani
The text was updated successfully, but these errors were encountered: