Trick the build into enabling IDE1006 but still allowing per-rule sev…

…erity configuration

eng/.editorconfig

@@ -0,0 +1,12 @@
+# Diagnostics with a default severity of suggestion or lower (including IDE* rules) do not run during command line
+# builds unless they have been elevated to warning or greater using the compiler-designated syntax. Since the compiler
+# syntax prevents the use of fine-grained severity configuration for rules like IDE1006 (Naming styles), we use this
+# configuration file to only force the severity to warning for a single known file in the compilation.
+
+[CodeAnalysisSource.{cs,vb}]
+
+# IDE1006: Naming styles
+dotnet_diagnostic.IDE1006.severity = warning
+
+# SA1518: Code should not contain blank lines at the end of the file
+dotnet_diagnostic.SA1518.severity = none

eng/CodeAnalysis.src.globalconfig

@@ -1726,7 +1726,8 @@ dotnet_diagnostic.IDE0230.severity = suggestion
 dotnet_diagnostic.IDE1005.severity = warning
 
 # IDE1006: Naming styles
-dotnet_diagnostic.IDE1006.severity = silent
+# This rule is configured by individual rules in .editorconfig. Do not override the severity here.
+#dotnet_diagnostic.IDE1006.severity = silent
 
 # IDE2000: Allow multiple blank lines
 dotnet_diagnostic.IDE2000.severity = silent

eng/CodeAnalysisSource.cs

@@ -0,0 +1 @@
+

eng/CodeAnalysisSource.vb

@@ -0,0 +1 @@
+

eng/CodeStyle.props

@@ -18,4 +18,12 @@
 
   </PropertyGroup>
 
+  <ItemGroup Condition="'$(Language)' == 'C#'">
+    <Compile Include="$(MSBuildThisFileDirectory)CodeAnalysisSource.cs" Visible="false" />
+  </ItemGroup>
+
+  <ItemGroup Condition="'$(Language)' == 'VB'">
+    <Compile Include="$(MSBuildThisFileDirectory)CodeAnalysisSource.vb" Visible="false" />
+  </ItemGroup>
+
 </Project>