Add code check CI tests, add docs about ReferenceResolution, and other cleanups (#1044)
Changes: * Add a step which checks that generated code is up to date * Copy over the documentation on how to work with `<reference>` * Fixup a broken reference in the .sln * Fix the casing on Microsoft.Extensions.ValueStopwatch.Sources * Remove some unused references and variables
This commit is contained in:
parent
f87c01b129
commit
e5ee01f97b
|
|
@ -6,6 +6,14 @@
|
|||
<PackageTags>$(PackageTags);analyzers</PackageTags>
|
||||
<NoWarn>$(NoWarn);CS1591</NoWarn>
|
||||
<BuildOutputTargetFolder>analyzers/dotnet/cs/</BuildOutputTargetFolder>
|
||||
<!--
|
||||
Except for analyzer unit tests, analyzers should not be referenced by other projects in this repo. Analyzers cannot be used as
|
||||
a project reference. The SDK currently only supports using analyzers as a PackageReference. This flag prevents this project from
|
||||
being used as a `<Reference>`, which indicates that a reference is interchangeable between ProjectRef and PackageRef.
|
||||
-->
|
||||
<IsProjectReferenceProvider>false</IsProjectReferenceProvider>
|
||||
<UseLatestPackageReferences>true</UseLatestPackageReferences>
|
||||
<SuppressDependenciesWhenPacking>true</SuppressDependenciesWhenPacking>
|
||||
<IsPackable>true</IsPackable>
|
||||
<IsShipping>false</IsShipping>
|
||||
</PropertyGroup>
|
||||
|
|
|
|||
Loading…
Reference in New Issue