validation class that serve many classes but as build conflict

i have solution of many projects (.NET), with project dependencies.

i need to create validation class that serve many classes, this class shall be at the end of the dependency order, to be able to "know" many types, but shall be invoke be some projects above his dependency order.

what is the software architecture can support\overcome this conflict?