8c75a8ea2b
* Prepare for strict coherency Strict coherency means that if your repo declares a dependency with a CPD attribute, the CPD parent must have a direct dependency on that dependency. This means for aspnetcore that it should add a dependency on System.Resources.Extensions because aspnetcore-tooling needs it. Reasons for this approach over the current approach: - This eliminates some ambiguous tie-breaking scenarios that are very problematic and dangerous in servicing - Those tie breaking scenarios require the use of BAR to break the ties. If the DB data were to be lost then the tie-breaking would do unexpected things. |
||
|---|---|---|
| .. | ||
| common | ||
| docker | ||
| helix | ||
| scripts | ||
| targets | ||
| tools | ||
| AfterSigning.targets | ||
| AfterSolutionBuild.targets | ||
| AllRulesDisabled.ruleset | ||
| Baseline.Designer.props | ||
| Baseline.xml | ||
| Build.props | ||
| CodeGen.proj | ||
| Common.props | ||
| Dependencies.props | ||
| GenAPI.exclusions.txt | ||
| LicenseHeader.txt | ||
| PoliCheckExclusions.xml | ||
| ProjectReferences.props | ||
| PublishSymbols.proj | ||
| Publishing.props | ||
| QuarantinedTests.AfterArcade.props | ||
| QuarantinedTests.BeforeArcade.props | ||
| SharedFramework.External.props | ||
| SharedFramework.Local.props | ||
| SignCheckExclusionsFile.txt | ||
| Signing.props | ||
| Tools.props | ||
| Version.Details.xml | ||
| Versions.props | ||
| Workarounds.props | ||
| Workarounds.targets | ||
| WorkaroundsImported.targets | ||
| configure-toolset.ps1 | ||
| configure-toolset.sh | ||
| empty.proj | ||
| sdl-tsa-vars.config | ||