You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, the command export-validation-docs does not accept an external assembly containing rules.
Suggestion
Create a new property that can point to an assembly which contains rules, for example, binskim.rules.dll. With that, we would be able to generate any rules from any provider who implement the Skimmer class. If the property was not supplied, so it will warn or use the self assembly (just the way we have now).
Change verb name to export-docs. This should pick up a default assembly to operate against (do we need to provide an API stub for this property?) Then we can add an argument that overrides this value. We could support passing multiple assemblies...
Today, the command
export-validation-docs
does not accept an external assembly containing rules.Suggestion
Create a new property that can point to an assembly which contains rules, for example, binskim.rules.dll. With that, we would be able to generate any rules from any provider who implement the
Skimmer
class. If the property was not supplied, so it will warn or use the self assembly (just the way we have now).@michaelcfanning
The text was updated successfully, but these errors were encountered: