admin/PowerShell-PowerShell
1
0
Fork 0
mirror of https://github.com/PowerShell/PowerShell synced 2026-06-08 12:12:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Change "operable" to "executable" (#13281)

Browse Source 
* Change "operable" to "executable" in a resource string
This commit is contained in:
Christopher Yeleighton
2020-08-06 13:02:43 +05:00
committed by GitHub
parent bedd3bc287
commit 8626937ac4
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/System.Management.Automation/engine/CommandDiscovery.cs
+1 -1
View File
@@ -865,7 +865,7 @@ namespace System.Management.Automation
if (result == null)
{
discoveryTracer.TraceError(
"'{0}' is not recognized as a cmdlet, function, operable program or script file.",
"'{0}' is not recognized as a cmdlet, function, executable program or script file.",
commandName);
CommandNotFoundException e =
src/System.Management.Automation/resources/DiscoveryExceptions.resx
+2 -2
View File
@@ -133,7 +133,7 @@
<value>Cannot process the cmdlet. A cmdlet name must consist of a verb and noun pair separated by '-'.</value>
</data>
<data name="CommandNotFoundException" xml:space="preserve">
<value>The term '{0}' is not recognized as the name of a cmdlet, function, script file, or operable program.
<value>The term '{0}' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.</value>
</data>
<data name="CmdletNotFoundException" xml:space="preserve">
@@ -143,7 +143,7 @@ Check the spelling of the name, or if a path was included, verify that the path
<value>The argument '{0}' is not recognized as a cmdlet, possibly because it does not derive from the Cmdlet or PSCmdlet classes: {1}</value>
</data>
<data name="AliasNotResolvedException" xml:space="preserve">
<value>Cannot resolve alias '{0}' because it refers to term '{1}', which is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again.</value>
<value>Cannot resolve alias '{0}' because it refers to term '{1}', which is not recognized as a cmdlet, function, executable program, or script file. Verify the term and try again.</value>
</data>
<data name="CommandNameNotCmdlet" xml:space="preserve">
<value>Parameter '{0}' with value '{1}' cannot be processed because it is not a cmdlet and cannot be processed by the CommandProcessor.</value>
test/powershell/Modules/Microsoft.PowerShell.Core/CompatiblePSEditions.Module.Tests.ps1
+1 -1
View File
@@ -502,7 +502,7 @@ Describe "Additional tests for Import-Module with WinCompat" -Tag "Feature" {
$ConfigPath = Join-Path $TestDrive 'powershell.config.json'
'{"DisableImplicitWinCompat" : "True","Microsoft.PowerShell:ExecutionPolicy": "RemoteSigned"}' | Out-File -Force $ConfigPath
& $pwsh -NoProfile -NonInteractive -settingsFile $ConfigPath -c "[System.Management.Automation.Internal.InternalTestHooks]::SetTestHook('TestWindowsPowerShellPSHomeLocation', `'$basePath`'); Test-$ModuleName2" *> $LogPath
$LogPath | Should -FileContentMatch 'not recognized as the name of a cmdlet'
$LogPath | Should -FileContentMatch 'not recognized as a name of a cmdlet'
}
It "Successfully auto-imports incompatible module during CommandDiscovery\ModuleAutoload if implicit WinCompat is Enabled in config" {