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
When creating an ArgumentException with a message parameter (and all calls should use that parameter, right?), the phrase "must not" should be preferred over "cannot" and "can not".
Presumably, this could be found by searching for the Regex @"\bcan ?not\b" (culture invariant, case insensitive) in the text of ArgumentExceptions and offering a code fix provider that changes the affected text to "must not".
The text was updated successfully, but these errors were encountered:
When creating an
ArgumentException
with a message parameter (and all calls should use that parameter, right?), the phrase "must not" should be preferred over "cannot" and "can not".Presumably, this could be found by searching for the Regex
@"\bcan ?not\b"
(culture invariant, case insensitive) in the text ofArgumentExceptions
and offering a code fix provider that changes the affected text to "must not".The text was updated successfully, but these errors were encountered: