Code Syntax Style: Built-In Type References
The C# type keywords and .NET Framework (CLR) type names are interchangeable for built-in C# types. If you prefer to stick to one or another style for built-in type names, ReSharper can help you maintain your preference.
You can maintain separate styles for static member access (for example, CLR type names — var str = String.Empty;) and for locals, members, and parameters (for example, keywords — void Foo(string str){ }.
ReSharper helps you enforce preferences for C# built-in types in the existing code and takes your preferences into account when it produces new code with code completion and performs refactorings.
Enforce preferences for C# built-in types
ReSharper checks all built-in type references for compliance with your preferences and if they do not comply it highlights such references and suggests the corresponding quick-fix. Default ReSharper's preferences say that the C# keywords are preferred.
If you change your preference, ReSharper will help you use .NET Framework type names:
Configure preferences for referencing C# built-in types
You can configure syntax style settings via EditorConfig. These settings can be stored in .editorconfig files on different levels of your solution hierarchy. The files are normally put under VCS so that settings defined there are shared among the project team.
If you have used ReSharper for Visual Studio or JetBrains Rider on your computer, or have opened the current solution using these tools, ReSharper for Visual Studio Code will read and apply your syntax style settings from .DotSettings files. However, any settings configured via .editorconfig will take precedence.
Configure preferences for built-in type references using EditorConfig
Open the desired .editorconfig file.
Add the required built-in type references properties to the file. For example:
builtin_type_reference_style = use_clr_name