aspnetcore/build
Ryan Nowak 1b47f44876
Add a top-level node for analyzers (#9906)
This is the first step, and just estabilishes a skeleton. The end goal
is organize our analyzers under this node because:
1. We're writing some 'top level' analyzers that depend on everything
else
2. We want to be able to service analyzers on the SDK schedule
(independent of runtime).

Next, we'll merge the MVC analyzers into this assembly since there's no
reason for them to be separate. The MVC API analyzers will remain a
separate package, but under this node. The component analyzers will
remain separate as they need to ship as a package, but will move under
this node as well.
2019-05-07 15:01:08 -07:00
..
Maestro
docker
tasks Updating SDK to 3.0.100-preview4-011136 2019-04-09 14:23:07 -07:00
AzureIntegration.targets
CodeSign.props
CodeSign.targets Update certificate for SignalR Java client (#9048) 2019-04-04 07:59:16 -07:00
SharedFx.targets
repo.props Add a top-level node for analyzers (#9906) 2019-05-07 15:01:08 -07:00
repo.targets EnableAzurePipelinesReporter for helix (#8094) 2019-05-05 22:15:10 -07:00
runtimes.props
sources.props Change IEndpointConventionBuilder extension methods to use generic argument (#8906) 2019-05-02 07:25:54 +12:00