Skip to content

Conversation

kapilmb
Copy link

@kapilmb kapilmb commented Nov 20, 2015

  • Renames CustomizedRulePath parameter to CustomRulePath.
  • Adds CustromizedRulePath as an alias of CustomRulePath.
  • Adds RecurseCustomRulePath switch to recursively retrieve custom rules.
  • Fixes a bug: CustomRulePath can now accept paths with a trailing
    backslash.
  • CustomRulePath parameter now takes only one string, instead of an array
    of strings.

* Renames CustomizedRulePath parameter to CustomRulePath.
* Adds CustromizedRulePath as an alias of CustomRulePath.
* Adds RecurseCustomRulePath switch to recursively retrieve custom rules.
* Fixes a bug: CustomRulePath can now accept paths with a trailing
backslash.
* CustomRulePath parameter now takes only one string, instead of an array
of strings.
@juneb
Copy link
Contributor

juneb commented Nov 20, 2015

Thanks so much! When this PR is accepted, I'll fix the help file.

kborle added 5 commits November 20, 2015 16:24
We have set the CustomRulePath parameter in the cmdlet implementation in LibraryUsage.tests.ps1 to "string[]" type whereas in the c# implementation it is of "string" type. If we set the CustomRulePath parameter here to "string", then the library usage test fails when run as an administrator. We want to note that the library usage test doesn't fail when run as a non-admin user. Even if we create a "[string[]]" type object and pass it to Initialize method,  the tests fail to run as an admin with the following error message.

Assert failed on "Initialize" with "7" argument(s): "Test failed due to terminating error: The module was expected to contain an assembly manifest. (Exception from HRESULT: 0x80131018)
@raghushantha
Copy link
Member

Sign-off.

kapilmb pushed a commit that referenced this pull request Nov 23, 2015
…Backslash

Renames CustomizedRulePath parameter and modifies its behavior.
@kapilmb kapilmb merged commit 48e2535 into development Nov 23, 2015
@kapilmb kapilmb deleted the FixCustomizedRulePathTrailingBackslash branch November 24, 2015 23:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants