SA1633 (file must have header) cannot be suppressed

We are having a build that turns warnings into errors. StyleCop is one source of warnings in our build. The rule SA1633 is enabled because we write most code ourselves, but sometimes we use code that was published under a license. We cannot add our copyright header to those files and because the diagnostic is being reported on the first character there is no way to suppress it.

Now the only way for us is to disable this rule for all files.

A possible solution could be to check for a #pragma warning disable SA1633 in the diagnostic provider (although this is duplicate work) to work around the limitations. Maybe we could also disable rules per file

Example of a non conforming header that cannot be changed:

#pragma warning disable SA1633 // File must have header
// *********************************************************
//
// Copyright (c) Microsoft. All rights reserved.
// This code is licensed under the MIT License (MIT).
// THIS CODE IS PROVIDED *AS IS* WITHOUT WARRANTY OF
// ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY
// IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR
// PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.
//
// *********************************************************
#pragma warning restore SA1633 // File must have header

[sharwell]

@chris-eaton Any rule can be disabled using a rule set file, or by adding it to the <NoWarn> list in the project file.

[umbarov]

IMO: It’s better to add suppressions to ProjectName.ruleset file and keep all suppressions in one file than messing suppressions with project file.