While farm administrators can always go and block a rogue solution from the Manage User Solutions screen, there is another proactive way in which solutions can be checked for validations at the time of activation, and any solutions failing validation can be prevented from activation. This can be achieved by developing a sandboxed solution validator.
The following steps are used to develop a solution validator:
1. Create a class inheriting from
2. Provide a
System.Runtime.InteropServices.Guid for the validator that will be used as
ProviderID for the validator.
3. Define a default constructor in the validator that takes no arguments.
4. Define another ...