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
I would rather keep global using statements in source files instead of in project files, but centralized in one GlobalUsings.cs file (or something similar) to make them easy to maintain. This also avoids the current problems with mixing normal and global usings in the same file. But a file with only global using statements in it triggers SA1200 with version 1.2.0-beta.556.
Would an exception to SA1200 be ok for files that contain nothing but global using statements and whitespace?
The text was updated successfully, but these errors were encountered:
I would rather keep global using statements in source files instead of in project files, but centralized in one GlobalUsings.cs file (or something similar) to make them easy to maintain. This also avoids the current problems with mixing normal and global usings in the same file. But a file with only global using statements in it triggers SA1200 with version 1.2.0-beta.556.
Would an exception to SA1200 be ok for files that contain nothing but global using statements and whitespace?
The text was updated successfully, but these errors were encountered: