Resolved problem with $Features due to Contains method being case sensit... #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…sitive The Contains method that is used throughout the Set-TargetResource function is case sensitive. This caused a configuration to fail if the features were specified in a case other than upper case which is how they are specified in the function. The easiest way to resolve this issue was to add a line to convert $Features to upper case.
|
Hi @mikefrobbins, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution! TTYL, MSBOT; |
vors
added a commit
that referenced
this pull request
Apr 28, 2015
Resolved problem with $Features due to Contains method being case sensit...
narrieta
pushed a commit
that referenced
this pull request
Aug 2, 2016
Test for xSQLServerPermission
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
...ive
The Contains method that is used throughout the Set-TargetResource
function is case sensitive. This caused a configuration to fail if the
features were specified in a case other than upper case which is how
they are specified in the function. The easiest way to resolve this
issue was to add a line to convert $Features to upper case.