Namespace Volo.Abp.Specifications

Classes

AndNotSpecification<T>

Represents the combined specification which indicates that the first specification can be satisifed by the given object whereas the second one cannot.

AndSpecification<T>

Represents the combined specification which indicates that both of the given specifications should be satisfied by the given object.

AnySpecification<T>

Represents the specification that can be satisfied by the given object in any circumstance.

CompositeSpecification<T>

Represents the base class for composite specifications.

Represents the extender for Expression[Func[T, bool]] type. This is part of the solution which solves the expression parameter problem when going to Entity Framework. For more information about this solution please refer to http://blogs.msdn.com/b/meek/archive/2008/05/02/linq-to-entities-combining-predicates.aspx.

ExpressionSpecification<T>

Represents the specification which is represented by the corresponding LINQ expression.

NoneSpecification<T>

Represents the specification that can be satisfied by the given object in no circumstance.

NotSpecification<T>

Represents the specification which indicates the semantics opposite to the given specification.

OrSpecification<T>

Represents the combined specification which indicates that either of the given specification should be satisfied by the given object.

Specification<T>

Represents the base class for specifications.

SpecificationExtensions

Interfaces

ICompositeSpecification<T>

Represents that the implemented classes are composite specifications.

ISpecification<T>

Represents that the implemented classes are specifications. For more information about the specification pattern, please refer to http://martinfowler.com/apsupp/spec.pdf.

ISpecificationParser<TCriteria>

Represents that the implemented classes are specification parsers that parses the given specification to a domain specific criteria object, such as the ICriteria instance in NHibernate.