อ่านในภาษาอังกฤษ

แชร์ผ่าน


Microsoft.Build.Experimental.BuildCheck Namespace

Classes

BuildCheckDataContext<T>

Data passed from infrastructure to build checks.

BuildCheckReplayModeConnector

The class that creates an IEventSource for binary log replay with BuildCheck enabled.

BuildCheckResult

Representation of a single report of a single finding from a Check Each rule has upfront known message format - so only the concrete arguments are added Optionally a location is attached - in the near future we might need to support multiple locations (for 2 cases - a) grouped result for multiple occurrences; b) a single report for a finding resulting from combination of multiple locations).

BuildFinishedCheckData

BuildCheck data indicating end of the build. This is the last event that can be received from the BuildCheck infrastructure.

Check

Base class for build checks. Same base will be used for custom and built-in checks. Check is a unit of build checks execution, but it can contain multiple rules - each representing a distinct violation.

CheckConfiguration

Configuration for a build check. Default values can be specified by the Check in code. Users can overwrite the defaults by explicit settings in the .editorconfig file. Each rule can have its own configuration, which can differ per each project. The EvaluationCheckScope setting must be same for all rules in the same check (but can differ between projects)

CheckData

Base for a data passed from infrastructure to build checks.

CheckRule

Represents a rule that is a unit of a build check. Check is a unit of executing the check, but it can be discovering multiple distinct violation types, for this reason a single Check can expose multiple CheckRules.

ConfigurationContext

Holder of configuration from .editorconfig file (not recognized by the infrastructure)

CustomConfigurationData

Holder for the key-value pairs of unstructured data from .editorconfig file, that were attribute to a particular rule, but were not recognized by the infrastructure. The configuration data that is recognized by the infrastructure is passed as CheckConfiguration.

EnvironmentVariableCheckData

BuildCheck OM data representing the environment variables used in a project file and its imports.

EvaluatedItemsCheckData

BuildCheck OM data representing the evaluated items of a project.

EvaluatedPropertiesCheckData

BuildCheck OM data representing the evaluated properties of a project.

ItemsHolder

Holder for evaluated items and item groups.

ItemTypeExtensions

Extension methods for ProjectItemElement.

ParsedItemsCheckData

BuildCheck OM data representing the evaluated items of a project - but only those defined within the project!. No explicit nor implicit imports are regarded. If you are looking the get all evaluated items - use EvaluatedItemsCheckData

ProjectImportedCheckData

Represents data for a check related to an imported project in MSBuild.

TaskInvocationCheckData

BuildCheck OM data representing a task executed by a project.

TaskInvocationCheckData.TaskParameter

Represents an input or output parameter of a task.

Interfaces

Enums

CheckResultSeverity

The severity of reported result (or preconfigured or user configured severity for a rule).

EvaluationCheckScope

For datasource events that can differentiate from where exactly they originate - e.g. For a condition string or AST - was that directly in the checked project or imported?

Ignored by infrastructure if the current datasource doesn't support this level of setting.