Also includes these bugfixes:
- WSManConfigProvider.GetHelpMaml: Tried to load XML from
MemoryStream that was created from file name string. Use XmlReader
instead.
- WSManConfigProvider.GetHelpMaml: Use Path.Combine instead of
platform-specific directory separator character.
- WSManConfigProvider.GetHelpMaml: CmdletHelpPath MAML XML element
attribute `ID` name casing seems inconsistent with other help.xml
files. XPath 1.0 does not support case-insensitive expressions,
use both `id` and `ID` in query.
- Add Pester test to verify that Get-Help shows provider-specific help.
Fixes#2088
ASSERT_TRUE("a"=="b") only reports that the strings do not match, hiding
their values.
ASSERT_STREQ("a","b") is a functionally equivalent test, but reports
back the values of the failing strings for easier troubleshooting.
PowerShell has some stubs to enable code to almost sort of work with things.
Some of the stubs try to say "Do not use me".
This commit corrects the grammar of the message.
Previously the message tried to apply a past tense form to `hit`,
but the past tense of `hit` is `hit`, and while breakpoints can
be hit, it's better to talk to the user about what should be done/
should not be done.
I think this logic was originally added with the assumption that any
hostname with a dot in it was an FQDN. I believe this is incorrect. The
hostname is the hostname regardless of included dots, and getting the
FQDN amounts to always querying for the canonical name.
Before this commit there were three spellings, one of which was a typo,
one was a variant spelling, and one was the dominant spelling.
Microsoft generally uses Hangul for its enums:
https://msdn.microsoft.com/en-us/library/cc250412.aspx
And this is the dominant spelling in general and as used in web browsers.
* Merge TFS 2064268: Under UMCI PowerShell should not block nested cmdlet invocation via runspace
* Update SessionState.cs
Fixed ExecutionContext property name error.
.NET CLI build 3546 started placing packages in:
~/.nuget/packages/microsoft.codeanalysis.common
instead of:
~/.nuget/packages/Microsoft.CodeAnalysis.Common
Where the previous (capitalized) version corresponded directly to the
package's name. Now they are all lower-cased.
The input loop reading from stdin did not handle multi-line input correctly
because it was adding a newline character where none was expected.
The fix was to not include the final newline character to accept input,
just like Console.ReadLine or PSReadline would.
George Chakhidze