From c8954b30bd3a5aebdcadf2ea786ff634a161f264 Mon Sep 17 00:00:00 2001 From: iSazonov Date: Wed, 6 Sep 2017 14:47:45 +0300 Subject: [PATCH 1/4] Replace 'Windows PowerShell' with 'PowerShell Core' in resx files --- .../resources/GetEventResources.resx | 2 +- .../resources/ComputerResources.resx | 2 +- .../ManagementMshSnapInResources.resx | 2 +- .../resources/ServiceResources.resx | 2 +- .../resources/Debugger.resx | 2 +- .../resources/FormatAndOut_out_gridview.resx | 2 +- .../resources/ImplicitRemotingStrings.resx | 10 +-- .../resources/ImportLocalizedDataStrings.resx | 6 +- .../resources/UtilityMshSnapinResources.resx | 4 +- .../CommandLineParameterParserStrings.resx | 22 +++--- .../resources/ConsoleHostStrings.resx | 8 +- .../ConsoleHostUserInterfaceStrings.resx | 2 +- .../resources/HostMshSnapinResources.resx | 4 +- .../resources/ManagedEntranceStrings.resx | 26 +++---- .../resources/ScheduledJobErrorStrings.resx | 14 ++-- .../resources/CertificateProviderStrings.resx | 2 +- .../resources/ExecutionPolicyCommands.resx | 4 +- .../resources/SecurityMshSnapinResources.resx | 4 +- .../resources/UtilsStrings.resx | 2 +- .../resources/WsManResources.resx | 2 +- .../resources/AutomationExceptions.resx | 20 ++--- .../resources/ConsoleInfoErrorStrings.resx | 30 +++---- .../resources/CoreMshSnapinResources.resx | 4 +- .../resources/CredUI.resx | 2 +- .../resources/CredentialAttributeStrings.resx | 2 +- .../resources/DiscoveryExceptions.resx | 6 +- .../resources/EventingResources.resx | 4 +- .../resources/HelpDisplayStrings.resx | 6 +- .../resources/HelpErrors.resx | 2 +- .../HostInterfaceExceptionsStrings.resx | 2 +- .../InternalHostUserInterfaceStrings.resx | 4 +- .../resources/Metadata.resx | 2 +- .../resources/Modules.resx | 22 +++--- .../resources/MshSnapInCmdletResources.resx | 8 +- .../resources/MshSnapinInfo.resx | 12 +-- .../resources/ParserStrings.resx | 4 +- .../resources/PowerShellStrings.resx | 18 ++--- .../resources/RemotingErrorIdStrings.resx | 78 +++++++++---------- .../resources/RunspaceInit.resx | 6 +- .../resources/RunspacePoolStrings.resx | 2 +- .../resources/RunspaceStrings.resx | 2 +- .../resources/Serialization.resx | 2 +- .../resources/SessionStateStrings.resx | 2 +- .../resources/SuggestionStrings.resx | 2 +- .../resources/TypesXmlStrings.resx | 2 +- 45 files changed, 183 insertions(+), 183 deletions(-) diff --git a/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx b/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx index b734263cad5..385f0faca7a 100644 --- a/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx +++ b/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx @@ -268,7 +268,7 @@ The defined template is following: This cmdlet can be run only on Microsoft Windows 7 and above. - This Windows PowerShell snap-in contains Windows Eventing and Performance Counter cmdlets. + This PowerShell Core snap-in contains Windows Eventing and Performance Counter cmdlets. Cannot find any performance counter sets in the {0} files that match the following: {1}. diff --git a/src/Microsoft.PowerShell.Commands.Management/resources/ComputerResources.resx b/src/Microsoft.PowerShell.Commands.Management/resources/ComputerResources.resx index aaa61c80568..e1c83d35b79 100644 --- a/src/Microsoft.PowerShell.Commands.Management/resources/ComputerResources.resx +++ b/src/Microsoft.PowerShell.Commands.Management/resources/ComputerResources.resx @@ -238,7 +238,7 @@ Verifying that the computer has been restarted... - Waiting for Windows PowerShell connectivity... + Waiting for PowerShell Core connectivity... Waiting for the restart to begin... diff --git a/src/Microsoft.PowerShell.Commands.Management/resources/ManagementMshSnapInResources.resx b/src/Microsoft.PowerShell.Commands.Management/resources/ManagementMshSnapInResources.resx index 124b9c8aae5..6447ae9c93b 100644 --- a/src/Microsoft.PowerShell.Commands.Management/resources/ManagementMshSnapInResources.resx +++ b/src/Microsoft.PowerShell.Commands.Management/resources/ManagementMshSnapInResources.resx @@ -118,7 +118,7 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - This Windows PowerShell Snap-In contains management cmdlets that are used to manage Windows components. + This PowerShell Core Snap-In contains management cmdlets that are used to manage Windows components. Microsoft Corporation diff --git a/src/Microsoft.PowerShell.Commands.Management/resources/ServiceResources.resx b/src/Microsoft.PowerShell.Commands.Management/resources/ServiceResources.resx index 5ae6c50ddc2..aa95beb97f0 100644 --- a/src/Microsoft.PowerShell.Commands.Management/resources/ServiceResources.resx +++ b/src/Microsoft.PowerShell.Commands.Management/resources/ServiceResources.resx @@ -199,6 +199,6 @@ Service '{1} ({0})' resume failed. - The command cannot be used to configure the service '{0}' because access to computer '{1}' is denied. Run Windows PowerShell as admin and run your command again. + The command cannot be used to configure the service '{0}' because access to computer '{1}' is denied. Run PowerShell Core as admin and run your command again. diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/Debugger.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/Debugger.resx index 668050350bf..0a13fda13b3 100644 --- a/src/Microsoft.PowerShell.Commands.Utility/resources/Debugger.resx +++ b/src/Microsoft.PowerShell.Commands.Utility/resources/Debugger.resx @@ -142,7 +142,7 @@ You cannot debug the default host Runspace using this cmdlet. To debug the default Runspace use the normal debugging commands from the host. - Cannot debug Runspace. The host has no debugger. Try debugging the Runspace inside the Windows PowerShell console or the Windows PowerShell ISE, both of which have built-in debuggers. + Cannot debug Runspace. The host has no debugger. Try debugging the Runspace inside the PowerShell Core console or the Visual Studio Code, both of which have built-in debuggers. Cannot debug Runspace. There is no host or host UI. The debugger requires a host and host UI for debugging. diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/FormatAndOut_out_gridview.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/FormatAndOut_out_gridview.resx index 8efa4d2bc5f..8135c994731 100644 --- a/src/Microsoft.PowerShell.Commands.Utility/resources/FormatAndOut_out_gridview.resx +++ b/src/Microsoft.PowerShell.Commands.Utility/resources/FormatAndOut_out_gridview.resx @@ -121,7 +121,7 @@ The data format is not supported by Out-GridView. - Microsoft .NET Framework 4.5 was installed while one or more Windows PowerShell sessions were running. To use the {0} cmdlet, close all Windows PowerShell windows, and then open a new Windows PowerShell window. + Microsoft .NET Framework 4.5 was installed while one or more PowerShell Core sessions were running. To use the {0} cmdlet, close all PowerShell Core windows, and then open a new PowerShell Core window. Type diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx index 45757177a0b..044338f0ed9 100644 --- a/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx +++ b/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx @@ -145,16 +145,16 @@ Extended type definition has been skipped for the '{0}' type because its name did not match the value of the FormatTypeName parameter. - Proxy creation has been skipped for the '{0}' command, because Windows PowerShell could not verify the safety of the command name. + Proxy creation has been skipped for the '{0}' command, because PowerShell Core could not verify the safety of the command name. - Proxy creation has been skipped for the '{0}' command, because Windows PowerShell could not verify the safety of a parameter name: '{1}'. + Proxy creation has been skipped for the '{0}' command, because PowerShell Core could not verify the safety of a parameter name: '{1}'. - Proxy creation has been skipped for the '{0}' command, because Windows PowerShell could not verify the safety of a parameter set name: '{1}'. + Proxy creation has been skipped for the '{0}' command, because PowerShell Core could not verify the safety of a parameter set name: '{1}'. - Proxy creation has been skipped for the '{0}' command, because Windows PowerShell could not verify the safety of a parameter alias name: '{1}'. + Proxy creation has been skipped for the '{0}' command, because PowerShell Core could not verify the safety of a parameter alias name: '{1}'. Proxy creation has been skipped for the following command: '{0}', because it would shadow an existing local command. Use the AllowClobber parameter if you want to shadow existing local commands. @@ -211,7 +211,7 @@ Completed. - Windows PowerShell Credential Request + PowerShell Core Credential Request Enter your credentials for {0}. diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/ImportLocalizedDataStrings.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/ImportLocalizedDataStrings.resx index 52be8133b17..19c3c8b115a 100644 --- a/src/Microsoft.PowerShell.Commands.Utility/resources/ImportLocalizedDataStrings.resx +++ b/src/Microsoft.PowerShell.Commands.Utility/resources/ImportLocalizedDataStrings.resx @@ -124,18 +124,18 @@ The FileName parameter was not specified. The FileName parameter is required when Import-LocalizedData is not called from a script file. - The following error occurred while Windows PowerShell was opening the data file '{0}': + The following error occurred while PowerShell Core was opening the data file '{0}': {1}. - The following error occurred while Windows PowerShell was loading the '{0}' script data file: + The following error occurred while PowerShell Core was loading the '{0}' script data file: {1}. The argument for the FileName parameter should not contain a path. - Cannot find the Windows PowerShell data file '{0}' in directory '{1}', or in any parent culture directories. + Cannot find the PowerShell Core data file '{0}' in directory '{1}', or in any parent culture directories. Cannot import localized data. The definition of additional supported commands is not allowed in this language mode. diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/UtilityMshSnapinResources.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/UtilityMshSnapinResources.resx index 387a0ebf0b9..a37dea6a48f 100644 --- a/src/Microsoft.PowerShell.Commands.Utility/resources/UtilityMshSnapinResources.resx +++ b/src/Microsoft.PowerShell.Commands.Utility/resources/UtilityMshSnapinResources.resx @@ -118,12 +118,12 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - This Windows PowerShell snap-in contains utility cmdlets that are used to view and organize data in different ways. + This PowerShell Core snap-in contains utility cmdlets that are used to view and organize data in different ways. Microsoft Corporation - Windows PowerShell utility snap-in + PowerShell Core utility snap-in diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/CommandLineParameterParserStrings.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/CommandLineParameterParserStrings.resx index 92ef090cd2a..a93c987f55b 100644 --- a/src/Microsoft.PowerShell.ConsoleHost/resources/CommandLineParameterParserStrings.resx +++ b/src/Microsoft.PowerShell.ConsoleHost/resources/CommandLineParameterParserStrings.resx @@ -141,11 +141,11 @@ PowerShell[.exe] -Help | -? | /? -PSConsoleFile - Loads the specified Windows PowerShell console file. To create a console - file, use Export-Console in Windows PowerShell. + Loads the specified PowerShell Core console file. To create a console + file, use Export-Console in PowerShell Core. -Version - Starts the specified version of Windows PowerShell. + Starts the specified version of PowerShell Core. -NoLogo Hides the copyright banner at startup. @@ -163,22 +163,22 @@ PowerShell[.exe] -Help | -? | /? Uses a single-threaded apartment for the execution thread. -OutputFormat - Determines how output from Windows PowerShell is formatted. Valid values + Determines how output from PowerShell Core is formatted. Valid values are "Text" (text strings) or "XML" (serialized CLIXML format). -InputFormat - Describes the format of data sent to Windows PowerShell. Valid values are + Describes the format of data sent to PowerShell Core. Valid values are "Text" (text strings) or "XML" (serialized CLIXML format). -ConfigurationName - Specifies a configuration endpoint in which Windows PowerShell is run. + Specifies a configuration endpoint in which PowerShell Core is run. This can be any endpoint registered on the local machine including the - default Windows PowerShell remoting endpoints or a custom endpoint having + default PowerShell Core remoting endpoints or a custom endpoint having specific user role capabilities. -Command Executes the specified commands (and any parameters) as though they were - typed at the Windows PowerShell command prompt, and then exits, unless + typed at the PowerShell Core command prompt, and then exits, unless NoExit is specified. The value of Command can be "-", a string. or a script block. @@ -186,14 +186,14 @@ PowerShell[.exe] -Help | -? | /? input. Script blocks must be enclosed in braces ({}). You can specify a script - block only when running PowerShell.exe in Windows PowerShell. The results + block only when running PowerShell.exe in PowerShell Core. The results of the script are returned to the parent shell as deserialized XML objects, not live objects. If the value of Command is a string, Command must be the last parameter in the command , because any characters typed after the command are interpreted as the command arguments. - To write a string that runs a Windows PowerShell command, use the format: + To write a string that runs a PowerShell Core command, use the format: "& {<command>}" where the quotation marks indicate a string and the invoke operator (&) causes the command to be run. @@ -249,7 +249,7 @@ EXAMPLES Processing -WindowStyle '{0}' failed: {1}. - Processing -File '{0}' failed because the file does not have a '.ps1' extension. Specify a valid Windows PowerShell script file name, and then try again. + Processing -File '{0}' failed because the file does not have a '.ps1' extension. Specify a valid PowerShell Core script file name, and then try again. The argument '{0}' is not recognized as the name of a script file. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostStrings.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostStrings.resx index 3446d2c36b1..76c4084c6bc 100644 --- a/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostStrings.resx +++ b/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostStrings.resx @@ -136,11 +136,11 @@ The shell cannot be started. A failure occurred during initialization: - An error has occurred that was not properly handled. Additional information is shown below. The Windows PowerShell process will exit. + An error has occurred that was not properly handled. Additional information is shown below. The PowerShell Core process will exit. ********************** -Windows PowerShell transcript start +PowerShell Core transcript start Start time: {0:yyyyMMddHHmmss} Username : {1}\{2} Machine : {3} ({4}) @@ -148,7 +148,7 @@ Machine : {3} ({4}) ********************** -Windows PowerShell transcript end +PowerShell Core transcript end End time: {0:yyyyMMddHHmmss} ********************** @@ -156,7 +156,7 @@ End time: {0:yyyyMMddHHmmss} An instance of the ConsoleHost class has already been created for this process. - Command '{0}' could not be run because some Windows PowerShell Snap-Ins did not load. + Command '{0}' could not be run because some PowerShell Core Snap-Ins did not load. Command '{0}' was not run as the session in which it was intended to run was either closed or broken diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostUserInterfaceStrings.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostUserInterfaceStrings.resx index f0daca5ab35..ea616fe7807 100644 --- a/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostUserInterfaceStrings.resx +++ b/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostUserInterfaceStrings.resx @@ -190,6 +190,6 @@ WARNING: {0} - Windows PowerShell is in NonInteractive mode. Read and Prompt functionality is not available. + PowerShell Core is in NonInteractive mode. Read and Prompt functionality is not available. diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/HostMshSnapinResources.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/HostMshSnapinResources.resx index c83ee2eafbc..2ddfb3f2bd6 100644 --- a/src/Microsoft.PowerShell.ConsoleHost/resources/HostMshSnapinResources.resx +++ b/src/Microsoft.PowerShell.ConsoleHost/resources/HostMshSnapinResources.resx @@ -118,12 +118,12 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - This Windows PowerShell snap-in contains cmdlets (such as Start-Transcript and Stop-Transcript) that are provided for use with the Windows PowerShell console host. + This PowerShell Core snap-in contains cmdlets (such as Start-Transcript and Stop-Transcript) that are provided for use with the PowerShell Core console host. Microsoft Corporation - Host Windows PowerShell Snap-In. + Host PowerShell Core Snap-In. diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/ManagedEntranceStrings.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/ManagedEntranceStrings.resx index ee05450c711..3918abaf1b8 100644 --- a/src/Microsoft.PowerShell.ConsoleHost/resources/ManagedEntranceStrings.resx +++ b/src/Microsoft.PowerShell.ConsoleHost/resources/ManagedEntranceStrings.resx @@ -134,11 +134,11 @@ Copyright (C) Microsoft Corporation. All rights reserved. PowerShell[.exe] -Help | -? | /? -PSConsoleFile - Loads the specified Windows PowerShell console file. To create a console - file, use Export-Console in Windows PowerShell. + Loads the specified PowerShell Core console file. To create a console + file, use Export-Console in PowerShell Core. -Version - Starts the specified version of Windows PowerShell. + Starts the specified version of PowerShell Core. Enter a version number with the parameter, such as "-version 2.0". -NoLogo @@ -155,7 +155,7 @@ PowerShell[.exe] -Help | -? | /? Start the shell using a multithreaded apartment. -NoProfile - Does not load the Windows PowerShell profile. + Does not load the PowerShell Core profile. -NonInteractive Does not present an interactive prompt to the user. @@ -164,11 +164,11 @@ PowerShell[.exe] -Help | -? | /? Present an interactive prompt to the user. -InputFormat - Describes the format of data sent to Windows PowerShell. Valid values are + Describes the format of data sent to PowerShell Core. Valid values are "Text" (text strings) or "XML" (serialized CLIXML format). -OutputFormat - Determines how output from Windows PowerShell is formatted. Valid values + Determines how output from PowerShell Core is formatted. Valid values are "Text" (text strings) or "XML" (serialized CLIXML format). -WindowStyle @@ -176,13 +176,13 @@ PowerShell[.exe] -Help | -? | /? -EncodedCommand Accepts a base-64-encoded string version of a command. Use this parameter - to submit commands to Windows PowerShell that require complex quotation + to submit commands to PowerShell Core that require complex quotation marks or curly braces. -ConfigurationName - Specifies a configuration endpoint in which Windows PowerShell is run. + Specifies a configuration endpoint in which PowerShell Core is run. This can be any endpoint registered on the local machine including the - default Windows PowerShell remoting endpoints or a custom endpoint having + default PowerShell Core remoting endpoints or a custom endpoint having specific user role capabilities. -File @@ -196,12 +196,12 @@ PowerShell[.exe] -Help | -? | /? -ExecutionPolicy Sets the default execution policy for the current session and saves it in the $env:PSExecutionPolicyPreference environment variable. - This parameter does not change the Windows PowerShell execution policy + This parameter does not change the PowerShell Core execution policy that is set in the registry. -Command Executes the specified commands (and any parameters) as though they were - typed at the Windows PowerShell command prompt, and then exits, unless + typed at the PowerShell Core command prompt, and then exits, unless NoExit is specified. The value of Command can be "-", a string. or a script block. @@ -210,14 +210,14 @@ PowerShell[.exe] -Help | -? | /? If the value of Command is a script block, the script block must be enclosed in braces ({}). You can specify a script block only when running PowerShell.exe - in Windows PowerShell. The results of the script block are returned to the + in PowerShell Core. The results of the script block are returned to the parent shell as deserialized XML objects, not live objects. If the value of Command is a string, Command must be the last parameter in the command , because any characters typed after the command are interpreted as the command arguments. - To write a string that runs a Windows PowerShell command, use the format: + To write a string that runs a PowerShell Core command, use the format: "& {<command>}" where the quotation marks indicate a string and the invoke operator (&) causes the command to be executed. diff --git a/src/Microsoft.PowerShell.ScheduledJob/resources/ScheduledJobErrorStrings.resx b/src/Microsoft.PowerShell.ScheduledJob/resources/ScheduledJobErrorStrings.resx index 9d80707dc05..18af6ed3205 100644 --- a/src/Microsoft.PowerShell.ScheduledJob/resources/ScheduledJobErrorStrings.resx +++ b/src/Microsoft.PowerShell.ScheduledJob/resources/ScheduledJobErrorStrings.resx @@ -134,7 +134,7 @@ There is no entry in Task Scheduler for scheduled job definition {0}. A new Task Scheduler entry has been created for this scheduled job definition. - Cannot get the {0} scheduled job because it is corrupted or in an irresolvable state. Because it cannot run, Windows PowerShell has deleted {0} and its results from the computer. To recreate the scheduled job, use the Register-ScheduledJob cmdlet. For more information about corrupted scheduled jobs, see about_Scheduled_Jobs_Troubleshooting. + Cannot get the {0} scheduled job because it is corrupted or in an irresolvable state. Because it cannot run, PowerShell Core has deleted {0} and its results from the computer. To recreate the scheduled job, use the Register-ScheduledJob cmdlet. For more information about corrupted scheduled jobs, see about_Scheduled_Jobs_Troubleshooting. {0} is the name of the scheduled job definition. @@ -192,7 +192,7 @@ Scheduled job definition {0}. - A directory not found error occurred while registering scheduled job definition {0}. Make sure you are running Windows PowerShell with elevated privileges. + A directory not found error occurred while registering scheduled job definition {0}. Make sure you are running PowerShell Core with elevated privileges. An error occurred while registering scheduled job definition {0}. Cannot add this definition object to the job store. @@ -231,7 +231,7 @@ The FilePath parameter is not valid. - Only Windows PowerShell script files are allowed for FilePath parameter. Specify a file with .ps1 extension. + Only PowerShell Core script files are allowed for FilePath parameter. Specify a file with .ps1 extension. The IdleDuration parameter cannot have a negative value. @@ -255,7 +255,7 @@ The WeeksInterval parameter value must be greater than zero. - An I/O failure occurred while updating the scheduled job definition {0}. This could mean a file is missing or corrupted, either in Task Scheduler or in the Windows PowerShell scheduled job store. You might need to create the scheduled job definition again. + An I/O failure occurred while updating the scheduled job definition {0}. This could mean a file is missing or corrupted, either in Task Scheduler or in the PowerShell Core scheduled job store. You might need to create the scheduled job definition again. {0} is the scheduled job definition name @@ -283,7 +283,7 @@ No Frequency type has been specified for this job trigger. One of the following job trigger frequencies must be specified: AtStartup, AtLogon, Once, Daily, Weekly. - An access denied error occurred while updating the scheduled job definition {0}. Try running Windows PowerShell with elevated user rights; that is, Run as Administrator. + An access denied error occurred while updating the scheduled job definition {0}. Try running PowerShell Core with elevated user rights; that is, Run as Administrator. {0} is the scheduled job definition name @@ -320,7 +320,7 @@ Weekly - An access denied error occurred when registering scheduled job definition {0}. Try running Windows PowerShell with elevated user rights; that is, Run As Administrator. + An access denied error occurred when registering scheduled job definition {0}. Try running PowerShell Core with elevated user rights; that is, Run As Administrator. Cannot convert a ScheduledJobTrigger object with TriggerFrequency value of {0}. @@ -334,7 +334,7 @@ {1} is the inner exception message from .Net serialization, or empty if no exception message. - Commands that interact with the host program, such as Write-Host, cannot be included in Windows PowerShell scheduled jobs because scheduled jobs do not interact with the host program. Use an alternate command that does not interact with the host program, such as Write-Output or Out-File. + Commands that interact with the host program, such as Write-Host, cannot be included in PowerShell Core scheduled jobs because scheduled jobs do not interact with the host program. Use an alternate command that does not interact with the host program, such as Write-Output or Out-File. The RepetitionInterval parameter value must be less than or equal to the RepetitionDuration parameter value. diff --git a/src/Microsoft.PowerShell.Security/resources/CertificateProviderStrings.resx b/src/Microsoft.PowerShell.Security/resources/CertificateProviderStrings.resx index bf4320ae3ac..5fd3f6b25d0 100644 --- a/src/Microsoft.PowerShell.Security/resources/CertificateProviderStrings.resx +++ b/src/Microsoft.PowerShell.Security/resources/CertificateProviderStrings.resx @@ -187,6 +187,6 @@ The operation is on user root store and UI is not allowed. - . The following error may be a result of user credentials required on the remote machine. See Enable-WSManCredSSP Cmdlet help on how to enable and use CredSSP for delegation with Windows PowerShell remoting. + . The following error may be a result of user credentials required on the remote machine. See Enable-WSManCredSSP Cmdlet help on how to enable and use CredSSP for delegation with PowerShell Core remoting. diff --git a/src/Microsoft.PowerShell.Security/resources/ExecutionPolicyCommands.resx b/src/Microsoft.PowerShell.Security/resources/ExecutionPolicyCommands.resx index bd7a0e348bd..ab053916583 100644 --- a/src/Microsoft.PowerShell.Security/resources/ExecutionPolicyCommands.resx +++ b/src/Microsoft.PowerShell.Security/resources/ExecutionPolicyCommands.resx @@ -118,7 +118,7 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - Windows PowerShell updated your execution policy successfully, but the setting is overridden by a policy defined at a more specific scope. Due to the override, your shell will retain its current effective execution policy of {0}. Type "Get-ExecutionPolicy -List" to view your execution policy settings. For more information please see "Get-Help Set-ExecutionPolicy". + PowerShell Core updated your execution policy successfully, but the setting is overridden by a policy defined at a more specific scope. Due to the override, your shell will retain its current effective execution policy of {0}. Type "Get-ExecutionPolicy -List" to view your execution policy settings. For more information please see "Get-Help Set-ExecutionPolicy". Contact your system administrator. @@ -136,6 +136,6 @@ The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose you to the security risks described in the about_Execution_Policies help topic at https://go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy? - {0} To change the execution policy for the default (LocalMachine) scope, start Windows PowerShell with the "Run as administrator" option. To change the execution policy for the current user, run "Set-ExecutionPolicy -Scope CurrentUser". + {0} To change the execution policy for the default (LocalMachine) scope, start PowerShell Core with the "Run as administrator" option. To change the execution policy for the current user, run "Set-ExecutionPolicy -Scope CurrentUser". diff --git a/src/Microsoft.PowerShell.Security/resources/SecurityMshSnapinResources.resx b/src/Microsoft.PowerShell.Security/resources/SecurityMshSnapinResources.resx index b7281417058..fbe8e61c921 100644 --- a/src/Microsoft.PowerShell.Security/resources/SecurityMshSnapinResources.resx +++ b/src/Microsoft.PowerShell.Security/resources/SecurityMshSnapinResources.resx @@ -118,12 +118,12 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - This Windows PowerShell Snap-In contains cmdlets to manage Windows PowerShell security. + This PowerShell Core Snap-In contains cmdlets to manage PowerShell Core security. Microsoft Corporation - Security Windows PowerShell Snap-In. + Security PowerShell Core Snap-In. diff --git a/src/Microsoft.PowerShell.Security/resources/UtilsStrings.resx b/src/Microsoft.PowerShell.Security/resources/UtilsStrings.resx index 869d5ed0151..e2a1882fb99 100644 --- a/src/Microsoft.PowerShell.Security/resources/UtilsStrings.resx +++ b/src/Microsoft.PowerShell.Security/resources/UtilsStrings.resx @@ -151,7 +151,7 @@ Central Access Policy identifier or name is not valid. If specifying an identifier, it must begin with S-1-17. If specifying a name, the policy must be applied on the target machine. - Windows PowerShell credential request + PowerShell Core credential request Enter your credentials. diff --git a/src/Microsoft.WSMan.Management/resources/WsManResources.resx b/src/Microsoft.WSMan.Management/resources/WsManResources.resx index 31837076b26..6aacf3ac850 100644 --- a/src/Microsoft.WSMan.Management/resources/WsManResources.resx +++ b/src/Microsoft.WSMan.Management/resources/WsManResources.resx @@ -308,7 +308,7 @@ Do you want to continue? This command cannot be used from the current path. Move to root path of the provider using cd\ and run your command again. - This Windows PowerShell snap-in contains cmdlets (such as Get-WSManInstance and Set-WSManInstance) that are used by the Windows PowerShell host to manage WSMan operations. + This PowerShell Core snap-in contains cmdlets (such as Get-WSManInstance and Set-WSManInstance) that are used by the PowerShell Core host to manage WSMan operations. This command cannot be used to remove the computer 'localhost' because it will always be connected. Give some other connected computer and run your command. diff --git a/src/System.Management.Automation/resources/AutomationExceptions.resx b/src/System.Management.Automation/resources/AutomationExceptions.resx index b765eed227e..02c70aa8d38 100644 --- a/src/System.Management.Automation/resources/AutomationExceptions.resx +++ b/src/System.Management.Automation/resources/AutomationExceptions.resx @@ -157,31 +157,31 @@ A script block that contains a top-level trap statement cannot be converted. - Cannot generate a Windows PowerShell object for a ScriptBlock dereferencing variables undeclared in the param(...) block. Name of undeclared variable: {0}. + Cannot generate a PowerShell Core object for a ScriptBlock dereferencing variables undeclared in the param(...) block. Name of undeclared variable: {0}. - Cannot generate a Windows PowerShell object for a ScriptBlock evaluating non-constant expressions. Non-constant expression: {0}. + Cannot generate a PowerShell Core object for a ScriptBlock evaluating non-constant expressions. Non-constant expression: {0}. - Cannot generate a Windows PowerShell object for a ScriptBlock evaluating dynamic expressions. Dynamic expression: {0}. + Cannot generate a PowerShell Core object for a ScriptBlock evaluating dynamic expressions. Dynamic expression: {0}. - Cannot generate a Windows PowerShell object for a ScriptBlock that tries to pass other script blocks inside argument values. + Cannot generate a PowerShell Core object for a ScriptBlock that tries to pass other script blocks inside argument values. - Cannot generate a Windows PowerShell object for a ScriptBlock which invokes pipelines, commands or functions to evaluate arguments of the main pipeline. + Cannot generate a PowerShell Core object for a ScriptBlock which invokes pipelines, commands or functions to evaluate arguments of the main pipeline. - Cannot generate a Windows PowerShell object for a ScriptBlock that uses dot sourcing. + Cannot generate a PowerShell Core object for a ScriptBlock that uses dot sourcing. - Cannot generate a Windows PowerShell object for a ScriptBlock that invokes other script blocks. + Cannot generate a PowerShell Core object for a ScriptBlock that invokes other script blocks. - The script block cannot be converted to a Windows PowerShell object because it contains forbidden redirection operators. + The script block cannot be converted to a PowerShell Core object because it contains forbidden redirection operators. - Cannot generate a Windows PowerShell object for a ScriptBlock that does not have an associated operation context. + Cannot generate a PowerShell Core object for a ScriptBlock that does not have an associated operation context. The command was stopped by the user. @@ -193,7 +193,7 @@ The script block cannot be converted to an open generic type. Define an appropriate closed generic type, and then retry. - Cannot generate a Windows PowerShell object for a ScriptBlock that starts a pipeline with an expression. + Cannot generate a PowerShell Core object for a ScriptBlock that starts a pipeline with an expression. Cannot create workflow. The type '{0}' from the '{1}' module could not be loaded. diff --git a/src/System.Management.Automation/resources/ConsoleInfoErrorStrings.resx b/src/System.Management.Automation/resources/ConsoleInfoErrorStrings.resx index 5270b69a830..bdc951d0bd7 100644 --- a/src/System.Management.Automation/resources/ConsoleInfoErrorStrings.resx +++ b/src/System.Management.Automation/resources/ConsoleInfoErrorStrings.resx @@ -133,7 +133,7 @@ The console file is not valid because the element {0} is not valid. - The console file is not valid because the Windows PowerShell snap-in name is missing. + The console file is not valid because the PowerShell Core snap-in name is missing. Attempting to save a console file with no name. Use Export-Console with the Path parameter to save the console file. @@ -151,49 +151,49 @@ The console file name extension is not valid. A console file name extension must be psc1. - Incorrect Windows PowerShell version {0}. Windows PowerShell version {1} is supported on this computer. + Incorrect PowerShell Core version {0}. PowerShell Core version {1} is supported on this computer. - Cannot find any Windows PowerShell snap-in information for {0}. + Cannot find any PowerShell Core snap-in information for {0}. - This is a system Windows PowerShell snap-in that is loaded by Windows PowerShell. + This is a system PowerShell Core snap-in that is loaded by PowerShell Core. - Cannot add Windows PowerShell snap-in {0} because it is already added. Verify the name of the snap-in, and then try again. + Cannot add PowerShell Core snap-in {0} because it is already added. Verify the name of the snap-in, and then try again. - Cannot remove the Windows PowerShell snap-in {0} because it is not loaded. Verify the name of the snap-in that you want to remove, and then try again. + Cannot remove the PowerShell Core snap-in {0} because it is not loaded. Verify the name of the snap-in that you want to remove, and then try again. - Cannot remove the Windows PowerShell snap-in {0} because it is a system snap-in. Verify the name of the snap-in that you want to remove, and then try again. + Cannot remove the PowerShell Core snap-in {0} because it is a system snap-in. Verify the name of the snap-in that you want to remove, and then try again. - Cannot load the Windows PowerShell snap-in because an error occurred while reading the registry information for the snap-in. + Cannot load the PowerShell Core snap-in because an error occurred while reading the registry information for the snap-in. - An error occurred while attempting to load the system Windows PowerShell snap-ins. Please contact Microsoft Customer Support Services. + An error occurred while attempting to load the system PowerShell Core snap-ins. Please contact Microsoft Customer Support Services. The following errors occurred when loading console {0}: {1} - Cannot load Windows PowerShell snap-in {0} because of the following error: {1} + Cannot load PowerShell Core snap-in {0} because of the following error: {1} - Windows PowerShell snap-in "{0}" loaded with the following warnings: {1} + PowerShell Core snap-in "{0}" loaded with the following warnings: {1} - The Windows PowerShell snap-in module {0} does not have the required Windows PowerShell snap-in strong name {1}. + The PowerShell Core snap-in module {0} does not have the required PowerShell Core snap-in strong name {1}. - The cmdlet '{0}' should not occur more than once in Windows PowerShell snap-in '{1}'. + The cmdlet '{0}' should not occur more than once in PowerShell Core snap-in '{1}'. - Windows PowerShell provider '{0}' should not occur more than once in Windows PowerShell snap-in '{1}'. + PowerShell Core provider '{0}' should not occur more than once in PowerShell Core snap-in '{1}'. - Windows PowerShell {0} is not supported in the current console. Windows PowerShell {1} is supported in the current console. + PowerShell Core {0} is not supported in the current console. PowerShell Core {1} is supported in the current console. The cmdlet is not supported by the custom shell. diff --git a/src/System.Management.Automation/resources/CoreMshSnapinResources.resx b/src/System.Management.Automation/resources/CoreMshSnapinResources.resx index 2cb77cf62dc..9861a3cad99 100644 --- a/src/System.Management.Automation/resources/CoreMshSnapinResources.resx +++ b/src/System.Management.Automation/resources/CoreMshSnapinResources.resx @@ -118,12 +118,12 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - This Windows PowerShell snap-in contains cmdlets used to manage components of Windows PowerShell. + This PowerShell Core snap-in contains cmdlets used to manage components of PowerShell Core. Microsoft Corporation - Core Windows PowerShell snap-in + Core PowerShell Core snap-in diff --git a/src/System.Management.Automation/resources/CredUI.resx b/src/System.Management.Automation/resources/CredUI.resx index ce16131a0f9..69f17a3ce80 100644 --- a/src/System.Management.Automation/resources/CredUI.resx +++ b/src/System.Management.Automation/resources/CredUI.resx @@ -118,7 +118,7 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - Windows PowerShell credential request + PowerShell Core credential request Enter your credentials. diff --git a/src/System.Management.Automation/resources/CredentialAttributeStrings.resx b/src/System.Management.Automation/resources/CredentialAttributeStrings.resx index 77bd6f648fe..67e3509f1ec 100644 --- a/src/System.Management.Automation/resources/CredentialAttributeStrings.resx +++ b/src/System.Management.Automation/resources/CredentialAttributeStrings.resx @@ -118,7 +118,7 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - Windows PowerShell credential request + PowerShell Core credential request Enter your credentials. diff --git a/src/System.Management.Automation/resources/DiscoveryExceptions.resx b/src/System.Management.Automation/resources/DiscoveryExceptions.resx index 2d7efadaba1..618734d2d2a 100644 --- a/src/System.Management.Automation/resources/DiscoveryExceptions.resx +++ b/src/System.Management.Automation/resources/DiscoveryExceptions.resx @@ -182,7 +182,7 @@ The #requires statement must be in one of the following formats: The script '{0}' cannot be run because it contained a "#requires" statement with a shell ID of {1} that is incompatible with the current shell. - The script '{0}' cannot be run because it contained a "#requires" statement for Windows PowerShell {1}. The version of Windows PowerShell that is required by the script does not match the currently running version of Windows PowerShell {2}. + The script '{0}' cannot be run because it contained a "#requires" statement for PowerShell Core {1}. The version of PowerShell Core that is required by the script does not match the currently running version of PowerShell Core {2}. The script '{0}' cannot be run because it contained a "#requires" statement for PowerShell editions '{1}'. The edition of PowerShell that is required by the script does not match the currently running PowerShell {2} edition. @@ -191,10 +191,10 @@ The #requires statement must be in one of the following formats: The script '{0}' cannot be run because the following snap-ins that are specified by the "#requires" statements of the script are missing: {1}. - A #requires statement has specified only a shellID. #Requires statements must specify a required Windows PowerShell snap-in when running in Windows PowerShell. + A #requires statement has specified only a shellID. #Requires statements must specify a required PowerShell Core snap-in when running in PowerShell Core. - The script '{0}' cannot be run because it contains a "#requires" statement for running as Administrator. The current Windows PowerShell session is not running as Administrator. Start Windows PowerShell by using the Run as Administrator option, and then try running the script again. + The script '{0}' cannot be run because it contains a "#requires" statement for running as Administrator. The current PowerShell Core session is not running as Administrator. Start PowerShell Core by using the Run as Administrator option, and then try running the script again. {0} (Version {1}) diff --git a/src/System.Management.Automation/resources/EventingResources.resx b/src/System.Management.Automation/resources/EventingResources.resx index 87a2facf379..fa8eb9c177d 100644 --- a/src/System.Management.Automation/resources/EventingResources.resx +++ b/src/System.Management.Automation/resources/EventingResources.resx @@ -124,10 +124,10 @@ Cannot register for the specified event. An event with the name '{0}' does not exist. - Windows PowerShell cannot subscribe to Windows RT events. + PowerShell Core cannot subscribe to Windows RT events. - Cannot register for the specified event. The event source identifier '{0}' is reserved for the Windows PowerShell engine. + Cannot register for the specified event. The event source identifier '{0}' is reserved for the PowerShell Core engine. This operation is not supported on remote instances. diff --git a/src/System.Management.Automation/resources/HelpDisplayStrings.resx b/src/System.Management.Automation/resources/HelpDisplayStrings.resx index 54dfbd813bc..32b15d4916f 100644 --- a/src/System.Management.Automation/resources/HelpDisplayStrings.resx +++ b/src/System.Management.Automation/resources/HelpDisplayStrings.resx @@ -334,10 +334,10 @@ (All) - No Windows PowerShell modules were found that match the following pattern: {0}. Verify the pattern and then try the command again. + No PowerShell Core modules were found that match the following pattern: {0}. Verify the pattern and then try the command again. - No Windows PowerShell modules were found that match the specified FullyQualifiedModule {0}. Verify the FullyQualifiedModule value and then try the command again. + No PowerShell Core modules were found that match the specified FullyQualifiedModule {0}. Verify the FullyQualifiedModule value and then try the command again. Help content cannot be found. Make sure the server is available and the help content location is properly defined in the HelpInfo XML. @@ -466,7 +466,7 @@ To update help again, add the Force parameter to your command. The root level element of the help content must be "helpItems". - The Update-Help cmdlet downloads the most current Help files for Windows PowerShell modules, and installs them on your computer. For more information about the Update-Help cmdlet, see https://go.microsoft.com/fwlink/?LinkId=210614. + The Update-Help cmdlet downloads the most current Help files for PowerShell Core modules, and installs them on your computer. For more information about the Update-Help cmdlet, see https://go.microsoft.com/fwlink/?LinkId=210614. Do you want to run Update-Help? diff --git a/src/System.Management.Automation/resources/HelpErrors.resx b/src/System.Management.Automation/resources/HelpErrors.resx index 13156eb21a1..d719e2242f6 100644 --- a/src/System.Management.Automation/resources/HelpErrors.resx +++ b/src/System.Management.Automation/resources/HelpErrors.resx @@ -175,7 +175,7 @@ Cannot get Help from a remote runspace, because the runspace has not been opened. Open the runspace by running an implicit remoting command, and then try running the command to get Help again. - Access is denied. The command could not update Help topics for the Windows PowerShell core modules, or for any modules in the $pshome\Modules directory. To update these Help topics, start Windows PowerShell by using the "Run as Administrator" command, and try running Update-Help again. + Access is denied. The command could not update Help topics for the PowerShell Core core modules, or for any modules in the $pshome\Modules directory. To update these Help topics, start PowerShell Core by using the "Run as Administrator" command, and try running Update-Help again. To use the {0}, install Windows PowerShell ISE by using Server Manager, and then restart this application. ({1}) diff --git a/src/System.Management.Automation/resources/HostInterfaceExceptionsStrings.resx b/src/System.Management.Automation/resources/HostInterfaceExceptionsStrings.resx index cbe385c9c9d..8fdbdaa08a3 100644 --- a/src/System.Management.Automation/resources/HostInterfaceExceptionsStrings.resx +++ b/src/System.Management.Automation/resources/HostInterfaceExceptionsStrings.resx @@ -121,7 +121,7 @@ An error of type "{0}" has occurred. - A command that prompts the user failed because the host program or the command type does not support user interaction. Try a host program that supports user interaction, such as the Windows PowerShell Console or Windows PowerShell ISE, and remove prompt-related commands from command types that do not support user interaction, such as Windows PowerShell workflows. + A command that prompts the user failed because the host program or the command type does not support user interaction. Try a host program that supports user interaction, such as the PowerShell Core Console, and remove prompt-related commands from command types that do not support user interaction, such as PowerShell Core workflows. A command that prompts the user failed because the host program or the command type does not support user interaction. The host was attempting to request confirmation with the following message: {0} diff --git a/src/System.Management.Automation/resources/InternalHostUserInterfaceStrings.resx b/src/System.Management.Automation/resources/InternalHostUserInterfaceStrings.resx index 4e0a5e7da92..a110f1ef05b 100644 --- a/src/System.Management.Automation/resources/InternalHostUserInterfaceStrings.resx +++ b/src/System.Management.Automation/resources/InternalHostUserInterfaceStrings.resx @@ -197,7 +197,7 @@ ********************** -Windows PowerShell transcript start +PowerShell Core transcript start Start time: {0:yyyyMMddHHmmss} Username: {1} RunAs User: {2} @@ -210,7 +210,7 @@ Process ID: {7} ********************** -Windows PowerShell transcript end +PowerShell Core transcript end End time: {0:yyyyMMddHHmmss} ********************** diff --git a/src/System.Management.Automation/resources/Metadata.resx b/src/System.Management.Automation/resources/Metadata.resx index 762f8306770..14fd34fa551 100644 --- a/src/System.Management.Automation/resources/Metadata.resx +++ b/src/System.Management.Automation/resources/Metadata.resx @@ -223,7 +223,7 @@ The "{1}" validation script for the argument with value "{0}" did not return a result of True. Determine why the validation script failed, and then try the command again. - The "{0}" argument does not contain a valid Windows PowerShell version. Supply a valid version number and then try the command again. + The "{0}" argument does not contain a valid PowerShell Core version. Supply a valid version number and then try the command again. Cannot validate argument '{0}' because it is not a valid variable name. diff --git a/src/System.Management.Automation/resources/Modules.resx b/src/System.Management.Automation/resources/Modules.resx index 04cd9689e64..ebf534444d8 100644 --- a/src/System.Management.Automation/resources/Modules.resx +++ b/src/System.Management.Automation/resources/Modules.resx @@ -157,7 +157,7 @@ The module manifest '{0}' could not be processed because it is not a valid PowerShell module manifest file. Remove the elements that are not permitted: {1} - Processing the module manifest file '{0}' did not result in a valid manifest object. Update the file to contain a valid Windows PowerShell module manifest. A valid manifest can be created using the New-ModuleManifest cmdlet. + Processing the module manifest file '{0}' did not result in a valid manifest object. Update the file to contain a valid PowerShell Core module manifest. A valid manifest can be created using the New-ModuleManifest cmdlet. The '{0}' module cannot be imported because its manifest contains one or more members that are not valid. The valid manifest members are ({1}). Remove the members that are not valid ({2}), then try to import the module again. @@ -181,7 +181,7 @@ The version of the Common Language Runtime (CLR) on this computer is '{0}'. The module '{1}' requires a minimum CLR version of '{2}' to run. Verify that you are running the minimum required version of CLR, and then try again. - The version of Windows PowerShell on this computer is '{0}'. The module '{1}' requires a minimum Windows PowerShell version of '{2}' to run. Verify that you have the minimum required version of Windows PowerShell installed, and then try again. + The version of PowerShell Core on this computer is '{0}'. The module '{1}' requires a minimum PowerShell Core version of '{2}' to run. Verify that you have the minimum required version of PowerShell Core installed, and then try again. The module manifest member 'NestedModules' cannot be used if the 'ModuleToProcess' member is a binary module. Edit the module manifest file at '{0}', and then try again. @@ -346,10 +346,10 @@ The module '{0}' requires the following version of the .NET Framework: {1}. The required version is not installed. - The name of the current Windows PowerShell host is: '{0}'. The module '{1}' requires the following Windows PowerShell host: '{2}'. + The name of the current PowerShell Core host is: '{0}'. The module '{1}' requires the following PowerShell Core host: '{2}'. - The current Windows PowerShell host is: '{0}' (version {1}). The module '{2}' requires a minimum Windows PowerShell host version of '{3}' to run. + The current PowerShell Core host is: '{0}' (version {1}). The module '{2}' requires a minimum PowerShell Core host version of '{3}' to run. Module manifest for module '{0}' @@ -388,7 +388,7 @@ Description of the functionality provided by this module - Minimum version of the Windows PowerShell engine required by this module + Minimum version of the PowerShell Core engine required by this module Minimum version of the common language runtime (CLR) required by this module. {0} @@ -475,10 +475,10 @@ Minimum version of Microsoft .NET Framework required by this module. {0} - Name of the Windows PowerShell host required by this module + Name of the PowerShell Core host required by this module - Minimum version of the Windows PowerShell host required by this module + Minimum version of the PowerShell Core host required by this module Loading workflow {0} @@ -487,13 +487,13 @@ HelpInfo URI of this module - The item {0} that resolves to {1} is not located in the same directory as the module manifest or any of its subdirectories. Windows PowerShell looks for items referenced in the manifest only in paths relative to the manifest location. To fix this problem, move the item, and use a relative path to identify its location. + The item {0} that resolves to {1} is not located in the same directory as the module manifest or any of its subdirectories. PowerShell Core looks for items referenced in the manifest only in paths relative to the manifest location. To fix this problem, move the item, and use a relative path to identify its location. The workflow file name is not valid because it does not have the required .XAML file name extension. Run the New-ModuleManifest command again specifying a value for the WorkflowsToProcess parameter with this extension. - Because the {0} module is providing the PSDrive in the current Windows PowerShell session, no modules were removed. Change the current PSDrive provider, and then try removing modules again. + Because the {0} module is providing the PSDrive in the current PowerShell Core session, no modules were removed. Change the current PSDrive provider, and then try removing modules again. The workflow file name extension is not valid. The workflow file name {0} that is listed in the WorkflowsToProcess key of the module manifest does not have the required .XAML or .DLL file name extension. Edit the module manifest and correct the workflow file name. If you are using a .DLL file extension, then provide only one assembly name. @@ -514,7 +514,7 @@ Wildcard characters are not allowed in members 'ModuleToProcess', 'RootModule', or 'NestedModules' in the module manifest '{0}'. - The module '{0}' is a core module for Windows PowerShell. Add the Force parameter to your command to remove core modules. + The module '{0}' is a core module for PowerShell Core. Add the Force parameter to your command to remove core modules. The module manifest cannot contain both the 'ModuleToProcess' and 'RootModule' members. Change the module manifest file to remove one of these members at '{0}', and then try again. @@ -535,7 +535,7 @@ The required module '{0}' was not loaded because no valid module file was found in any module directory. - Some commands from module {0} cannot be imported over a CimSession. To get all the commands, verify that the remote server has Windows PowerShell remote management enabled, and then try adding the PSSession parameter to an Import-Module cmdlet. + Some commands from module {0} cannot be imported over a CimSession. To get all the commands, verify that the remote server has PowerShell Core remote management enabled, and then try adding the PSSession parameter to an Import-Module cmdlet. The module {0} cannot be imported over a CimSession. Try using the PSSession parameter of the Import-Module cmdlet. diff --git a/src/System.Management.Automation/resources/MshSnapInCmdletResources.resx b/src/System.Management.Automation/resources/MshSnapInCmdletResources.resx index 826b34e0946..7adcb713040 100644 --- a/src/System.Management.Automation/resources/MshSnapInCmdletResources.resx +++ b/src/System.Management.Automation/resources/MshSnapInCmdletResources.resx @@ -121,15 +121,15 @@ The operation cannot be performed. The specified cmdlet is not supported in a custom shell. - No Windows PowerShell snap-ins matching the pattern '{0}' were found. Check the pattern and then try the command again. + No PowerShell Core snap-ins matching the pattern '{0}' were found. Check the pattern and then try the command again. - The format of the specified snap-in name was not valid. Windows PowerShell snap-in names can only contain alpha-numeric characters, dashes, underscores and periods. Correct the name and then try the operation again. + The format of the specified snap-in name was not valid. PowerShell Core snap-in names can only contain alpha-numeric characters, dashes, underscores and periods. Correct the name and then try the operation again. - Cannot add Windows PowerShell snap-in {0} because it is a system Windows PowerShell module. Use Import-Module to load the module. + Cannot add PowerShell Core snap-in {0} because it is a system PowerShell Core module. Use Import-Module to load the module. - The custom Windows PowerShell snap-in is not supported in PowerShell Core. + The custom PowerShell Core snap-in is not supported in PowerShell Core. diff --git a/src/System.Management.Automation/resources/MshSnapinInfo.resx b/src/System.Management.Automation/resources/MshSnapinInfo.resx index 1c99f6149d8..93fbed47508 100644 --- a/src/System.Management.Automation/resources/MshSnapinInfo.resx +++ b/src/System.Management.Automation/resources/MshSnapinInfo.resx @@ -118,19 +118,19 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - Unable to access Windows PowerShell registry information. + Unable to access PowerShell Core registry information. - Unable to access Windows PowerShell PowerShellEngine registry information. + Unable to access PowerShell Core PowerShellEngine registry information. Unable to access PublicKeyToken information. - Version {0} of Windows PowerShell is not available on this computer. + Version {0} of PowerShell Core is not available on this computer. - The Windows PowerShell snap-in '{0}' is not installed on this computer. + The PowerShell Core snap-in '{0}' is not installed on this computer. The mandatory value {0} is not specified for registry key {1}. @@ -145,7 +145,7 @@ Cannot find required information in registry or missing key files. Cannot load some cmdlets. - No snap-ins have been registered for Windows PowerShell version {0}. + No snap-ins have been registered for PowerShell Core version {0}. Cannot retrieve the string resource because the reader has been disposed. @@ -154,6 +154,6 @@ Version value {0} is not specified or is incorrect for registry key {1}. - No [PSVersion] attribute was found for Windows PowerShell type {0}. Add a PSVersion attribute to the type using [PSVersion(Windows PowerShell SnapinBase.PSEngineVersion)]. + No [PSVersion] attribute was found for PowerShell Core type {0}. Add a PSVersion attribute to the type using [PSVersion(PowerShell Core SnapinBase.PSEngineVersion)]. diff --git a/src/System.Management.Automation/resources/ParserStrings.resx b/src/System.Management.Automation/resources/ParserStrings.resx index 3f43594b049..028de2d3dca 100644 --- a/src/System.Management.Automation/resources/ParserStrings.resx +++ b/src/System.Management.Automation/resources/ParserStrings.resx @@ -850,7 +850,7 @@ Possible matches are Flow of control cannot leave a Finally block. - Unrecoverable error in Windows PowerShell. + Unrecoverable error in PowerShell Core. An AST cannot be used as the child of more than one AST. To use this AST in another AST, call the Copy() method and use its result. @@ -925,7 +925,7 @@ Possible matches are The argument for the Module parameter is not valid. {0} - The argument for the Version parameter is not valid. Specify a valid Windows PowerShell version, in the format major.minor version. + The argument for the Version parameter is not valid. Specify a valid PowerShell Core version, in the format major.minor version. The argument for the {0} parameter is not valid. Specify a valid PowerShell edition. diff --git a/src/System.Management.Automation/resources/PowerShellStrings.resx b/src/System.Management.Automation/resources/PowerShellStrings.resx index 68848261139..a6e54f9ee34 100644 --- a/src/System.Management.Automation/resources/PowerShellStrings.resx +++ b/src/System.Management.Automation/resources/PowerShellStrings.resx @@ -142,7 +142,7 @@ Nested PowerShell instances cannot be invoked asynchronously. Use the Invoke method. - The {0} object was not created by calling {1} on this Windows PowerShell instance. + The {0} object was not created by calling {1} on this PowerShell Core instance. When the runspace is set to reuse a thread, the apartment state in the invocation settings must match the runspace. @@ -151,7 +151,7 @@ When the runspace is set to use the current thread, the apartment state in the invocation settings must match that of the current thread. - A command is required to add a parameter. A command must be added to the Windows PowerShell instance before adding a parameter. + A command is required to add a parameter. A command must be added to the PowerShell Core instance before adding a parameter. The keys in the dictionary must be strings. @@ -163,10 +163,10 @@ You can only begin receiving data on a PSJobProxy instance when it has been created with data streaming disabled. This operation can run only once. - GetJobForCommand is not supported when there is more than one command in the Windows PowerShell instance. + GetJobForCommand is not supported when there is more than one command in the PowerShell Core instance. - The Command property of a Windows PowerShell object cannot be empty. + The Command property of a PowerShell Core object cannot be empty. The PSJobProxy object can only be used for remote commands that return a job object. @@ -193,16 +193,16 @@ A job object cannot be reused. - This Windows PowerShell object cannot be connected because it is not associated with a remote runspace or runspace pool. + This PowerShell Core object cannot be connected because it is not associated with a remote runspace or runspace pool. The running command has been disconnected but is still running on the remote server. Reconnect to get command operation status and output data. - The operation cannot be performed because the current Windows PowerShell session is in the Disconnected state. Connect this Windows PowerShell session, and then either wait for the command to finish, or stop the command. + The operation cannot be performed because the current PowerShell Core session is in the Disconnected state. Connect this PowerShell Core session, and then either wait for the command to finish, or stop the command. - The operation cannot be performed because the current Windows PowerShell session is in the Disconnected state. Connect this Windows PowerShell session, and then try again. + The operation cannot be performed because the current PowerShell Core session is in the Disconnected state. Connect this PowerShell Core session, and then try again. The connection attempt to the remote command failed. @@ -215,7 +215,7 @@ The operation cannot be performed because a command is currently stopping. Wait for the command to complete stopping, and then try the operation again. - There is no Runspace available to run commands in this thread. You can provide one in the DefaultRunspace property of the System.Management.Automation.Runspaces.Runspace type. The current Windows PowerShell instance contains no command to invoke. + There is no Runspace available to run commands in this thread. You can provide one in the DefaultRunspace property of the System.Management.Automation.Runspaces.Runspace type. The current PowerShell Core instance contains no command to invoke. A command in which the value of AsJob is equal to false cannot be run through a PSJobProxy. @@ -226,7 +226,7 @@ PSJobProxy is the name of a class and should not be localized - A Windows PowerShell object cannot be created that uses the current runspace because there is no current runspace available. The current runspace might be starting, such as when it is created with an Initial Session State. + A PowerShell Core object cannot be created that uses the current runspace because there is no current runspace available. The current runspace might be starting, such as when it is created with an Initial Session State. PSJobProxy does not support this control method. diff --git a/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx b/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx index d81f6048b19..71eda94917d 100644 --- a/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx +++ b/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx @@ -172,7 +172,7 @@ Only administrators can override the Thread Options remotely. - Windows PowerShell Credential Request: {0} + PowerShell Core Credential Request: {0} Warning: A script or application on the remote computer {0} is requesting your credentials. Enter your credentials only if you trust the remote computer and the application or script that is requesting them. @@ -183,7 +183,7 @@ A script or application on the remote computer {0} is asking to read a line securely. Enter sensitive information, such as your credentials, only if you trust the remote computer and the application or script that is requesting it. - A script or application on the remote computer {0} is attempting to read the buffer contents on the Windows PowerShell host. For security reasons, this is not allowed; the call has been suppressed. + A script or application on the remote computer {0} is attempting to read the buffer contents on the PowerShell Core host. For security reasons, this is not allowed; the call has been suppressed. A script or application on the remote computer {0} is sending a prompt request. When you are prompted, enter sensitive information, such as credentials or passwords, only if you trust the remote computer and the application or script that is requesting the data. @@ -270,7 +270,7 @@ Error in decoding Maximum runspaces. - Error in decoding Windows PowerShellStateInfo. + Error in decoding PowerShell CoreStateInfo. Unexpected type of {0} property (expected {1}, got {2}). @@ -294,31 +294,31 @@ The client negotiation timer has expired. The negotiation time-out interval is {0} milliseconds. - Windows PowerShell client does not support the {0} {1} negotiated by the server. Make sure the server is compatible with the build {2} and the protocol version {3} of Windows PowerShell. + PowerShell Core client does not support the {0} {1} negotiated by the server. Make sure the server is compatible with the build {2} and the protocol version {3} of PowerShell Core. - {0}. Negotiation with the server failed. Make sure the server is compatible with the build {1} and the protocol version {2} of Windows PowerShell. + {0}. Negotiation with the server failed. Make sure the server is compatible with the build {1} and the protocol version {2} of PowerShell Core. The destination server has sent a request to close the session. - The server that is running Windows PowerShell does not support the {0} {1} negotiated by the client computer. Verify that the client computer is compatible with the build {2} and the protocol version {3} of Windows PowerShell. + The server that is running PowerShell Core does not support the {0} {1} negotiated by the client computer. Verify that the client computer is compatible with the build {2} and the protocol version {3} of PowerShell Core. - The server that is running Windows PowerShell does not support connect operations on the {0} {1} that is negotiated by the client computer. Make sure the client computer is compatible with the build {2} and the protocol version {3} of Windows PowerShell. + The server that is running PowerShell Core does not support connect operations on the {0} {1} that is negotiated by the client computer. Make sure the client computer is compatible with the build {2} and the protocol version {3} of PowerShell Core. - The server that is running Windows PowerShell cannot process the connect operation because the following information is not found or not valid: Client Capability information and Connect RunspacePool information. + The server that is running PowerShell Core cannot process the connect operation because the following information is not found or not valid: Client Capability information and Connect RunspacePool information. - The server that is running Windows PowerShell cannot process the connect operation because the server has either not been started, or it is shutting down. + The server that is running PowerShell Core cannot process the connect operation because the server has either not been started, or it is shutting down. - The server that is running Windows PowerShell cannot process the connect operation because the server runspace pool properties did not match the client computer specified properties. + The server that is running PowerShell Core cannot process the connect operation because the server runspace pool properties did not match the client computer specified properties. - {0}. Negotiation with the client failed. Make sure the client is compatible with the build {1} and the protocol version {2} of Windows PowerShell. + {0}. Negotiation with the client failed. Make sure the client is compatible with the build {1} and the protocol version {2} of PowerShell Core. The server negotiation timer has expired. The negotiation time-out interval is {0} milliseconds. @@ -327,7 +327,7 @@ The client computer has sent a request to close the session. - An error has occurred which Windows PowerShell cannot handle. A remote session might have ended. + An error has occurred which PowerShell Core cannot handle. A remote session might have ended. The server did not respond with an encrypted session key within the specified time-out period. @@ -342,7 +342,7 @@ Attempting to close the session. - Windows PowerShell cannot close the remote session properly. The session is in an undefined state because it was not opened or connected after being disconnected. Windows PowerShell will try to force the session to close on the local computer, but the session might not be closed on the remote computer. To close a remote session properly, first open it or connect it. + PowerShell Core cannot close the remote session properly. The session is in an undefined state because it was not opened or connected after being disconnected. PowerShell Core will try to force the session to close on the local computer, but the session might not be closed on the remote computer. To close a remote session properly, first open it or connect it. Could not close the session. @@ -459,10 +459,10 @@ Inter-process communication (IPC) transport does not support connect operations. - An EndpointConfiguration with Id {0} does not exist on the remote server. Contact your Windows PowerShell administrator, or the owner or creator of the endpoint configuration. + An EndpointConfiguration with Id {0} does not exist on the remote server. Contact your PowerShell Core administrator, or the owner or creator of the endpoint configuration. - The EndpointConfiguration with the {0} identifier is not in a valid initial session state on the remote computer. Contact your Windows PowerShell administrator, or the owner or creator of the endpoint configuration. + The EndpointConfiguration with the {0} identifier is not in a valid initial session state on the remote computer. Contact your PowerShell Core administrator, or the owner or creator of the endpoint configuration. The mandatory value {0} is not specified for the {1} registry key. @@ -471,7 +471,7 @@ The mandatory value {0} is not in the correct format for registry key {1}. The expected format is 'string'. - "{0}" must specify a Windows PowerShell script file that ends with extension ".ps1". + "{0}" must specify a PowerShell Core script file that ends with extension ".ps1". The {0} parameter is already specified in the {1} section. Contact your administrator to make sure that {0} is specified only once. @@ -552,7 +552,7 @@ The path specified as the value of the FilePath parameter is not from the FileSystem provider. - The value of the FilePath parameter must be a Windows PowerShell script file. Enter the path to a file with a .ps1 file name extension and try the command again. + The value of the FilePath parameter must be a PowerShell Core script file. Enter the path to a file with a .ps1 file name extension and try the command again. One or more computer names are not valid. If you are trying to pass a URI, use the -ConnectionUri parameter, or pass URI objects instead of strings. @@ -582,7 +582,7 @@ Remote Command: {0}, associated with a job that has an ID of "{1}". - The command cannot retrieve the jobs of the specified computers. The ComputerName parameter can be used only with jobs created by using Windows PowerShell remoting. + The command cannot retrieve the jobs of the specified computers. The ComputerName parameter can be used only with jobs created by using PowerShell Core remoting. The Session parameter can be used only with PSRemotingJob objects. @@ -654,13 +654,13 @@ Session configuration "{0}" was not found. - Session configuration "{0}" is not a Windows PowerShell-based shell. + Session configuration "{0}" is not a PowerShell Core-based shell. Session configuration "{0}" is a PowerShell Core-based shell. Please use PowerShell Core to modify it. - Session configuration "{0}" is a Windows PowerShell-based shell. Please use Windows PowerShell to modify it. + Session configuration "{0}" is a PowerShell Core-based shell. Please use PowerShell Core to modify it. No session configuration matches criteria "{0}". @@ -672,13 +672,13 @@ Name: {0} - Name: {0}. This lets administrators remotely run Windows PowerShell commands on this computer. + Name: {0}. This lets administrators remotely run PowerShell Core commands on this computer. Cannot delete temporary file {0}. Reason for failure: {1}. - The new shell was successfully registered, but Windows PowerShell cannot delete the temporary file {0}. Reason for failure: {1}. + The new shell was successfully registered, but PowerShell Core cannot delete the temporary file {0}. Reason for failure: {1}. Cannot write the shell configuration data into the temporary file {0}. Reason for failure: {1}. @@ -687,13 +687,13 @@ Running command "{0}" to create a new session configuration. - Name: {0} SDDL: {1}. This lets selected users remotely run Windows PowerShell commands on this computer. + Name: {0} SDDL: {1}. This lets selected users remotely run PowerShell Core commands on this computer. Running command "{0}" to remove a session configuration. - Running command "{0}" to get Windows PowerShell-based session configurations. + Running command "{0}" to get PowerShell Core-based session configurations. Running command "{0}" to update the session configuration properties. @@ -721,7 +721,7 @@ Do you want to continue? Performing operation "{0}". - Name: {0} SDDL: {1}. This lets selected users remotely run Windows PowerShell commands on this computer. + Name: {0} SDDL: {1}. This lets selected users remotely run PowerShell Core commands on this computer. Running command "{0}" to disable the session configuration. @@ -737,7 +737,7 @@ Do you want to continue? 4. Restore the value of the LocalAccountTokenFilterPolicy to 0, which restricts remote access to members of the Administrators group on the computer. - Access is denied. To run this cmdlet, start Windows PowerShell with the "Run as administrator" option. + Access is denied. To run this cmdlet, start PowerShell Core with the "Run as administrator" option. Restarting WinRM service @@ -846,7 +846,7 @@ Do you want to continue? The WriteEvents parameter cannot be used without the Wait parameter. - Windows PowerShell {0} is not installed. Install Windows PowerShell {0}, and then try again. + PowerShell Core {0} is not installed. Install PowerShell Core {0}, and then try again. The following type cannot be instantiated because its constructor is not public: {0}. @@ -933,14 +933,14 @@ Do you want to continue? The command cannot find a PSSession that has the name "{0}". - Windows PowerShell remoting is not supported in the Windows Preinstallation Environment (WinPE). + PowerShell Core remoting is not supported in the Windows Preinstallation Environment (WinPE). Changes made by {0} cannot take effect until the WinRM service is restarted. {0} may need to restart the WinRM service if a configuration using this name has recently been unregistered, certain system data structures may still be cached. In that case, a restart of WinRM may be required. -All WinRM sessions connected to Windows PowerShell session configurations, such as Microsoft.PowerShell and session configurations that are created with the Register-PSSessionConfiguration cmdlet, are disconnected. +All WinRM sessions connected to PowerShell Core session configurations, such as Microsoft.PowerShell and session configurations that are created with the Register-PSSessionConfiguration cmdlet, are disconnected. You are running in a remote session and have selected the Force option which means the WinRM service may restart.If the WinRM service restarts then this remote session will be terminated and you will need to create a new session to continue @@ -952,7 +952,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such A running command could not be found for this PSSession. - The Microsoft .NET Framework 2.0, which is required for Windows PowerShell 2.0, is not installed. Install the .NET Framework 2.0 and retry. + The Microsoft .NET Framework 2.0, which is required for PowerShell Core 2.0, is not installed. Install the .NET Framework 2.0 and retry. The remote pipeline failed. @@ -1030,7 +1030,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such Modules to import when applied to a session - Version of the Windows PowerShell engine to use when applied to a session + Version of the PowerShell Core engine to use when applied to a session Processor architecture to use when applied to a session @@ -1196,7 +1196,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such The PSSession is in a disconnected state and is not available for connection. - The Hyper-V Module for Windows PowerShell is not available on this machine. + The Hyper-V Module for PowerShell Core is not available on this machine. Failed to launch PowerShell process inside container with id {0}. @@ -1318,7 +1318,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such One or more jobs are in a suspended or disconnected state, and cannot continue without additional user input. Specify the -Force parameter to continue to a completed, failed, or stopped state. - When RunAs is enabled in a Windows PowerShell session configuration, the Windows security model cannot enforce a security boundary between different user sessions that are created by using this endpoint. Verify that the Windows PowerShell runspace configuration is restricted to only the necessary set of cmdlets and capabilities. + When RunAs is enabled in a PowerShell Core session configuration, the Windows security model cannot enforce a security boundary between different user sessions that are created by using this endpoint. Verify that the PowerShell Core runspace configuration is restricted to only the necessary set of cmdlets and capabilities. The job was suspended successfully by adding the Force parameter. @@ -1333,7 +1333,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such The workflow job "{0}" was stopped. Receive-Job is only displaying partial results. - Disconnected sessions are supported only when the remote computer is running Windows PowerShell 3.0 or a later version of Windows PowerShell. + Disconnected sessions are supported only when the remote computer is running PowerShell Core 3.0 or a later version of PowerShell Core. Memory usage of a cmdlet has exceeded a warning level. To avoid this situation, try one of the following: 1) Lower the rate at which CIM operations produce data (for example, by passing a low value to the ThrottleLimit parameter), 2) Increase the rate at which data is consumed by downstream cmdlets, or 3) Use the Invoke-Command cmdlet to run the whole pipeline on the server. The cmdlet that exceeded a warning level of memory usage was started by the following command line: {0} @@ -1342,7 +1342,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such PSSession {0} was created using the EnableNetworkAccess parameter and can only be reconnected from the local computer. - You are currently in a Windows PowerShell PSSession and cannot use the Enter-PSSession cmdlet to enter another PSSession. + You are currently in a PowerShell Core PSSession and cannot use the Enter-PSSession cmdlet to enter another PSSession. Cannot start job. The language mode for this session is incompatible with the system-wide language mode. @@ -1354,7 +1354,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such Cannot exit a nested pipeline because the pipeline is not in the nested state. - The Windows PowerShell server session is not in a valid state for running nested commands. No nested commands can be run in this session. + The PowerShell Core server session is not in a valid state for running nested commands. No nested commands can be run in this session. Cannot invoke a nested command on the remote session because a nested command is already running. @@ -1366,7 +1366,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such The remote session command is currently stopped in the debugger. Use the Enter-PSSession cmdlet to connect interactively to the remote session and automatically enter into the console debugger. - The remote session to which you are connected does not support remote debugging. You must connect to a remote computer that is running Windows PowerShell {0} or greater. + The remote session to which you are connected does not support remote debugging. You must connect to a remote computer that is running PowerShell Core {0} or greater. Because the session state for session {0}, {1}, {2} is not equal to Open, you cannot run a command in the session. The session state is {3}. @@ -1408,13 +1408,13 @@ All WinRM sessions connected to Windows PowerShell session configurations, such The Named Pipe server listener used for process attach is already running. - Enter-PSHostProcess does not support entering the same Windows PowerShell session it is running in. + Enter-PSHostProcess does not support entering the same PowerShell Core session it is running in. Multiple processes were found with this name {0}. Use the process Id to specify a single process to enter. - Cannot enter process {0} because it has not loaded the Windows PowerShell engine. + Cannot enter process {0} because it has not loaded the PowerShell Core engine. No process was found with Id: {0}. diff --git a/src/System.Management.Automation/resources/RunspaceInit.resx b/src/System.Management.Automation/resources/RunspaceInit.resx index d036c4897c0..18fc9989b89 100644 --- a/src/System.Management.Automation/resources/RunspaceInit.resx +++ b/src/System.Management.Automation/resources/RunspaceInit.resx @@ -130,7 +130,7 @@ The run objects available to cmdlets - Version information for current Windows PowerShell session + Version information for current PowerShell Core session Current process ID @@ -199,10 +199,10 @@ Displays errors with a description of the error class - Culture of the current Windows PowerShell session + Culture of the current PowerShell Core session - UI culture of the current Windows PowerShell session + UI culture of the current PowerShell Core session Variable to hold all default <cmdlet:parameter, value> pairs diff --git a/src/System.Management.Automation/resources/RunspacePoolStrings.resx b/src/System.Management.Automation/resources/RunspacePoolStrings.resx index 721d758c7c5..5a2ae22b735 100644 --- a/src/System.Management.Automation/resources/RunspacePoolStrings.resx +++ b/src/System.Management.Automation/resources/RunspacePoolStrings.resx @@ -160,7 +160,7 @@ The Disconnect operation is not supported on the server. The server must be running Windows PowerShell 3.0 or greater for remote runspace pool disconnection support. - This runspace pool {0} is not configured to provide disconnected Windows PowerShell objects for commands running on the remote server. Use the RunspacePool class GetRunspacePools() static method to query the server and return runspace pool objects that are configured to do this. + This runspace pool {0} is not configured to provide disconnected PowerShell Core objects for commands running on the remote server. Use the RunspacePool class GetRunspacePools() static method to query the server and return runspace pool objects that are configured to do this. This runspace pool cannot be connected because the corresponding server side runspace pool is connected to another client. diff --git a/src/System.Management.Automation/resources/RunspaceStrings.resx b/src/System.Management.Automation/resources/RunspaceStrings.resx index 82de66e1127..377d38cd9af 100644 --- a/src/System.Management.Automation/resources/RunspaceStrings.resx +++ b/src/System.Management.Automation/resources/RunspaceStrings.resx @@ -237,7 +237,7 @@ - You have entered a session that is currently stopped at a debug breakpoint inside a running command or script. Use the Windows PowerShell command line debugger to continue debugging. + You have entered a session that is currently stopped at a debug breakpoint inside a running command or script. Use the PowerShell Core command line debugger to continue debugging. diff --git a/src/System.Management.Automation/resources/Serialization.resx b/src/System.Management.Automation/resources/Serialization.resx index 87be4cd35e1..ba7d2ed1ce5 100644 --- a/src/System.Management.Automation/resources/Serialization.resx +++ b/src/System.Management.Automation/resources/Serialization.resx @@ -178,7 +178,7 @@ The key type {0} is not valid. The PSPrimitiveDictionary class accepts only keys of the type System.String. - The type of the value {0} is not valid. The PSPrimitiveDictionary class accepts only values of types that are fully serializable over Windows PowerShell remoting. See the Help topic about_Remoting for a list of fully-serializable types. + The type of the value {0} is not valid. The PSPrimitiveDictionary class accepts only values of types that are fully serializable over PowerShell Core remoting. See the Help topic about_Remoting for a list of fully-serializable types. Could not decrypt data. The data was not encrypted with this key. diff --git a/src/System.Management.Automation/resources/SessionStateStrings.resx b/src/System.Management.Automation/resources/SessionStateStrings.resx index 736018f1b1e..9a2782e1d01 100644 --- a/src/System.Management.Automation/resources/SessionStateStrings.resx +++ b/src/System.Management.Automation/resources/SessionStateStrings.resx @@ -451,7 +451,7 @@ Cannot find a provider with the name '{0}'. - Cannot find a provider with the name '{0}'. The name is not in the proper format. A provider name can only be alphanumeric characters, or a Windows PowerShell snap-in name that is followed by a single '\', followed by alphanumeric characters. + Cannot find a provider with the name '{0}'. The name is not in the proper format. A provider name can only be alphanumeric characters, or a PowerShell Core snap-in name that is followed by a single '\', followed by alphanumeric characters. '{0}' resolved to more than one provider name. Possible matches include:{1}. diff --git a/src/System.Management.Automation/resources/SuggestionStrings.resx b/src/System.Management.Automation/resources/SuggestionStrings.resx index 5c0d2be84ce..ca8d2a81ed7 100644 --- a/src/System.Management.Automation/resources/SuggestionStrings.resx +++ b/src/System.Management.Automation/resources/SuggestionStrings.resx @@ -124,7 +124,7 @@ The Use-Transaction cmdlet is intended for scripting of transaction-enabled .NET objects. Its ScriptBlock should contain nothing else. - The command {0} was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: "{1}". See "get-help about_Command_Precedence" for more details. + The command {0} was not found, but does exist in the current location. PowerShell Core does not load commands from the current location by default. If you trust this command, instead type: "{1}". See "get-help about_Command_Precedence" for more details. Rule must be a ScriptBlock for dynamic match types. diff --git a/src/System.Management.Automation/resources/TypesXmlStrings.resx b/src/System.Management.Automation/resources/TypesXmlStrings.resx index d4a67dc9952..935061366d4 100644 --- a/src/System.Management.Automation/resources/TypesXmlStrings.resx +++ b/src/System.Management.Automation/resources/TypesXmlStrings.resx @@ -160,7 +160,7 @@ Cannot create an instance of the type converter for type {0} due to exception: {1}. - Windows PowerShell cannot create an instance of the type adapter for the type {0} because of the following exception: {1}. + PowerShell Core cannot create an instance of the type adapter for the type {0} because of the following exception: {1}. The adapted type "{0}" is not valid. From 7fca929ebb8192c3fb59756507b41e0d5042fe88 Mon Sep 17 00:00:00 2001 From: iSazonov Date: Wed, 6 Sep 2017 15:23:19 +0300 Subject: [PATCH 2/4] Fix test --- .../Microsoft.Powershell.Host/Start-Transcript.Tests.ps1 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/powershell/Modules/Microsoft.Powershell.Host/Start-Transcript.Tests.ps1 b/test/powershell/Modules/Microsoft.Powershell.Host/Start-Transcript.Tests.ps1 index 9b56407e748..8e15a1bf649 100644 --- a/test/powershell/Modules/Microsoft.Powershell.Host/Start-Transcript.Tests.ps1 +++ b/test/powershell/Modules/Microsoft.Powershell.Host/Start-Transcript.Tests.ps1 @@ -133,7 +133,7 @@ Describe "Start-Transcript, Stop-Transcript tests" -tags "CI" { Test-Path $transcriptFilePath | Should be $true $transcriptFilePath | Should contain "Before Dispose" - $transcriptFilePath | Should contain "Windows PowerShell transcript end" + $transcriptFilePath | Should contain "PowerShell Core transcript end" } } \ No newline at end of file From 49c08c38cceec3dd209cd244fc589d0bc5929dbb Mon Sep 17 00:00:00 2001 From: iSazonov Date: Thu, 7 Sep 2017 06:53:38 +0300 Subject: [PATCH 3/4] Replace 'PowerShell Core' with 'PowerShell' --- .../resources/GetEventResources.resx | 2 +- .../resources/ComputerResources.resx | 2 +- .../ManagementMshSnapInResources.resx | 2 +- .../resources/ServiceResources.resx | 2 +- .../resources/Debugger.resx | 2 +- .../resources/FormatAndOut_out_gridview.resx | 2 +- .../resources/ImplicitRemotingStrings.resx | 10 +-- .../resources/ImportLocalizedDataStrings.resx | 6 +- .../resources/NewObjectStrings.resx | 2 +- .../resources/UtilityMshSnapinResources.resx | 4 +- .../CommandLineParameterParserStrings.resx | 22 ++--- .../resources/ConsoleHostStrings.resx | 8 +- .../ConsoleHostUserInterfaceStrings.resx | 2 +- .../resources/HostMshSnapinResources.resx | 4 +- .../resources/ManagedEntranceStrings.resx | 26 +++--- .../resources/ScheduledJobErrorStrings.resx | 14 ++-- .../resources/CertificateProviderStrings.resx | 2 +- .../resources/ExecutionPolicyCommands.resx | 4 +- .../resources/SecurityMshSnapinResources.resx | 4 +- .../resources/UtilsStrings.resx | 2 +- .../resources/WsManResources.resx | 2 +- .../resources/AutomationExceptions.resx | 20 ++--- .../resources/ConsoleInfoErrorStrings.resx | 30 +++---- .../resources/CoreMshSnapinResources.resx | 4 +- .../resources/CredUI.resx | 2 +- .../resources/CredentialAttributeStrings.resx | 2 +- .../resources/DiscoveryExceptions.resx | 6 +- .../resources/EventingResources.resx | 4 +- .../resources/HelpDisplayStrings.resx | 6 +- .../resources/HelpErrors.resx | 2 +- .../HostInterfaceExceptionsStrings.resx | 2 +- .../InternalHostUserInterfaceStrings.resx | 4 +- .../resources/Metadata.resx | 2 +- .../resources/Modules.resx | 24 +++--- .../resources/MshSnapInCmdletResources.resx | 8 +- .../resources/MshSnapinInfo.resx | 12 +-- .../resources/ParserStrings.resx | 10 +-- .../resources/PowerShellStrings.resx | 18 ++-- .../resources/RemotingErrorIdStrings.resx | 84 +++++++++---------- .../resources/RunspaceInit.resx | 6 +- .../resources/RunspacePoolStrings.resx | 2 +- .../resources/RunspaceStrings.resx | 2 +- .../resources/Serialization.resx | 2 +- .../resources/SessionStateStrings.resx | 2 +- .../resources/SuggestionStrings.resx | 2 +- .../resources/TypesXmlStrings.resx | 2 +- .../Start-Transcript.Tests.ps1 | 2 +- 47 files changed, 192 insertions(+), 192 deletions(-) diff --git a/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx b/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx index 385f0faca7a..20b9fe45eb7 100644 --- a/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx +++ b/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx @@ -268,7 +268,7 @@ The defined template is following: This cmdlet can be run only on Microsoft Windows 7 and above. - This PowerShell Core snap-in contains Windows Eventing and Performance Counter cmdlets. + This PowerShell snap-in contains Windows Eventing and Performance Counter cmdlets. Cannot find any performance counter sets in the {0} files that match the following: {1}. diff --git a/src/Microsoft.PowerShell.Commands.Management/resources/ComputerResources.resx b/src/Microsoft.PowerShell.Commands.Management/resources/ComputerResources.resx index e1c83d35b79..f295fed1f2e 100644 --- a/src/Microsoft.PowerShell.Commands.Management/resources/ComputerResources.resx +++ b/src/Microsoft.PowerShell.Commands.Management/resources/ComputerResources.resx @@ -238,7 +238,7 @@ Verifying that the computer has been restarted... - Waiting for PowerShell Core connectivity... + Waiting for PowerShell connectivity... Waiting for the restart to begin... diff --git a/src/Microsoft.PowerShell.Commands.Management/resources/ManagementMshSnapInResources.resx b/src/Microsoft.PowerShell.Commands.Management/resources/ManagementMshSnapInResources.resx index 6447ae9c93b..73de4f80a24 100644 --- a/src/Microsoft.PowerShell.Commands.Management/resources/ManagementMshSnapInResources.resx +++ b/src/Microsoft.PowerShell.Commands.Management/resources/ManagementMshSnapInResources.resx @@ -118,7 +118,7 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - This PowerShell Core Snap-In contains management cmdlets that are used to manage Windows components. + This PowerShell Snap-In contains management cmdlets that are used to manage Windows components. Microsoft Corporation diff --git a/src/Microsoft.PowerShell.Commands.Management/resources/ServiceResources.resx b/src/Microsoft.PowerShell.Commands.Management/resources/ServiceResources.resx index aa95beb97f0..0f99f066c8c 100644 --- a/src/Microsoft.PowerShell.Commands.Management/resources/ServiceResources.resx +++ b/src/Microsoft.PowerShell.Commands.Management/resources/ServiceResources.resx @@ -199,6 +199,6 @@ Service '{1} ({0})' resume failed. - The command cannot be used to configure the service '{0}' because access to computer '{1}' is denied. Run PowerShell Core as admin and run your command again. + The command cannot be used to configure the service '{0}' because access to computer '{1}' is denied. Run PowerShell as admin and run your command again. diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/Debugger.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/Debugger.resx index 0a13fda13b3..d53cadfb0ca 100644 --- a/src/Microsoft.PowerShell.Commands.Utility/resources/Debugger.resx +++ b/src/Microsoft.PowerShell.Commands.Utility/resources/Debugger.resx @@ -142,7 +142,7 @@ You cannot debug the default host Runspace using this cmdlet. To debug the default Runspace use the normal debugging commands from the host. - Cannot debug Runspace. The host has no debugger. Try debugging the Runspace inside the PowerShell Core console or the Visual Studio Code, both of which have built-in debuggers. + Cannot debug Runspace. The host has no debugger. Try debugging the Runspace inside the PowerShell console or with Visual Studio Code, both of which have built-in debuggers. Cannot debug Runspace. There is no host or host UI. The debugger requires a host and host UI for debugging. diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/FormatAndOut_out_gridview.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/FormatAndOut_out_gridview.resx index 8135c994731..e5bdb6dc12b 100644 --- a/src/Microsoft.PowerShell.Commands.Utility/resources/FormatAndOut_out_gridview.resx +++ b/src/Microsoft.PowerShell.Commands.Utility/resources/FormatAndOut_out_gridview.resx @@ -121,7 +121,7 @@ The data format is not supported by Out-GridView. - Microsoft .NET Framework 4.5 was installed while one or more PowerShell Core sessions were running. To use the {0} cmdlet, close all PowerShell Core windows, and then open a new PowerShell Core window. + Microsoft .NET Framework 4.5 was installed while one or more PowerShell sessions were running. To use the {0} cmdlet, close all PowerShell windows, and then open a new PowerShell window. Type diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx index 044338f0ed9..48d1fea7c34 100644 --- a/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx +++ b/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx @@ -145,16 +145,16 @@ Extended type definition has been skipped for the '{0}' type because its name did not match the value of the FormatTypeName parameter. - Proxy creation has been skipped for the '{0}' command, because PowerShell Core could not verify the safety of the command name. + Proxy creation has been skipped for the '{0}' command, because PowerShell could not verify the safety of the command name. - Proxy creation has been skipped for the '{0}' command, because PowerShell Core could not verify the safety of a parameter name: '{1}'. + Proxy creation has been skipped for the '{0}' command, because PowerShell could not verify the safety of a parameter name: '{1}'. - Proxy creation has been skipped for the '{0}' command, because PowerShell Core could not verify the safety of a parameter set name: '{1}'. + Proxy creation has been skipped for the '{0}' command, because PowerShell could not verify the safety of a parameter set name: '{1}'. - Proxy creation has been skipped for the '{0}' command, because PowerShell Core could not verify the safety of a parameter alias name: '{1}'. + Proxy creation has been skipped for the '{0}' command, because PowerShell could not verify the safety of a parameter alias name: '{1}'. Proxy creation has been skipped for the following command: '{0}', because it would shadow an existing local command. Use the AllowClobber parameter if you want to shadow existing local commands. @@ -211,7 +211,7 @@ Completed. - PowerShell Core Credential Request + PowerShell Credential Request Enter your credentials for {0}. diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/ImportLocalizedDataStrings.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/ImportLocalizedDataStrings.resx index 19c3c8b115a..8bd19d60ac3 100644 --- a/src/Microsoft.PowerShell.Commands.Utility/resources/ImportLocalizedDataStrings.resx +++ b/src/Microsoft.PowerShell.Commands.Utility/resources/ImportLocalizedDataStrings.resx @@ -124,18 +124,18 @@ The FileName parameter was not specified. The FileName parameter is required when Import-LocalizedData is not called from a script file. - The following error occurred while PowerShell Core was opening the data file '{0}': + The following error occurred while PowerShell was opening the data file '{0}': {1}. - The following error occurred while PowerShell Core was loading the '{0}' script data file: + The following error occurred while PowerShell was loading the '{0}' script data file: {1}. The argument for the FileName parameter should not contain a path. - Cannot find the PowerShell Core data file '{0}' in directory '{1}', or in any parent culture directories. + Cannot find the PowerShell data file '{0}' in directory '{1}', or in any parent culture directories. Cannot import localized data. The definition of additional supported commands is not allowed in this language mode. diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/NewObjectStrings.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/NewObjectStrings.resx index cce49c375f9..e8064bfe483 100644 --- a/src/Microsoft.PowerShell.Commands.Utility/resources/NewObjectStrings.resx +++ b/src/Microsoft.PowerShell.Commands.Utility/resources/NewObjectStrings.resx @@ -142,6 +142,6 @@ Cannot create type. Only core types are supported in this language mode. - {0} Please note that Single-Threaded Apartment is not supported in PowerShell Core. + {0} Please note that Single-Threaded Apartment is not supported in PowerShell. diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/UtilityMshSnapinResources.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/UtilityMshSnapinResources.resx index a37dea6a48f..3bca38847db 100644 --- a/src/Microsoft.PowerShell.Commands.Utility/resources/UtilityMshSnapinResources.resx +++ b/src/Microsoft.PowerShell.Commands.Utility/resources/UtilityMshSnapinResources.resx @@ -118,12 +118,12 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - This PowerShell Core snap-in contains utility cmdlets that are used to view and organize data in different ways. + This PowerShell snap-in contains utility cmdlets that are used to view and organize data in different ways. Microsoft Corporation - PowerShell Core utility snap-in + PowerShell utility snap-in diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/CommandLineParameterParserStrings.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/CommandLineParameterParserStrings.resx index a93c987f55b..1484a3fce2b 100644 --- a/src/Microsoft.PowerShell.ConsoleHost/resources/CommandLineParameterParserStrings.resx +++ b/src/Microsoft.PowerShell.ConsoleHost/resources/CommandLineParameterParserStrings.resx @@ -141,11 +141,11 @@ PowerShell[.exe] -Help | -? | /? -PSConsoleFile - Loads the specified PowerShell Core console file. To create a console - file, use Export-Console in PowerShell Core. + Loads the specified PowerShell console file. To create a console + file, use Export-Console in PowerShell. -Version - Starts the specified version of PowerShell Core. + Starts the specified version of PowerShell. -NoLogo Hides the copyright banner at startup. @@ -163,22 +163,22 @@ PowerShell[.exe] -Help | -? | /? Uses a single-threaded apartment for the execution thread. -OutputFormat - Determines how output from PowerShell Core is formatted. Valid values + Determines how output from PowerShell is formatted. Valid values are "Text" (text strings) or "XML" (serialized CLIXML format). -InputFormat - Describes the format of data sent to PowerShell Core. Valid values are + Describes the format of data sent to PowerShell. Valid values are "Text" (text strings) or "XML" (serialized CLIXML format). -ConfigurationName - Specifies a configuration endpoint in which PowerShell Core is run. + Specifies a configuration endpoint in which PowerShell is run. This can be any endpoint registered on the local machine including the - default PowerShell Core remoting endpoints or a custom endpoint having + default PowerShell remoting endpoints or a custom endpoint having specific user role capabilities. -Command Executes the specified commands (and any parameters) as though they were - typed at the PowerShell Core command prompt, and then exits, unless + typed at the PowerShell command prompt, and then exits, unless NoExit is specified. The value of Command can be "-", a string. or a script block. @@ -186,14 +186,14 @@ PowerShell[.exe] -Help | -? | /? input. Script blocks must be enclosed in braces ({}). You can specify a script - block only when running PowerShell.exe in PowerShell Core. The results + block only when running PowerShell.exe in PowerShell. The results of the script are returned to the parent shell as deserialized XML objects, not live objects. If the value of Command is a string, Command must be the last parameter in the command , because any characters typed after the command are interpreted as the command arguments. - To write a string that runs a PowerShell Core command, use the format: + To write a string that runs a PowerShell command, use the format: "& {<command>}" where the quotation marks indicate a string and the invoke operator (&) causes the command to be run. @@ -249,7 +249,7 @@ EXAMPLES Processing -WindowStyle '{0}' failed: {1}. - Processing -File '{0}' failed because the file does not have a '.ps1' extension. Specify a valid PowerShell Core script file name, and then try again. + Processing -File '{0}' failed because the file does not have a '.ps1' extension. Specify a valid PowerShell script file name, and then try again. The argument '{0}' is not recognized as the name of a script file. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostStrings.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostStrings.resx index 76c4084c6bc..e7a3d10ec30 100644 --- a/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostStrings.resx +++ b/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostStrings.resx @@ -136,11 +136,11 @@ The shell cannot be started. A failure occurred during initialization: - An error has occurred that was not properly handled. Additional information is shown below. The PowerShell Core process will exit. + An error has occurred that was not properly handled. Additional information is shown below. The PowerShell process will exit. ********************** -PowerShell Core transcript start +PowerShell transcript start Start time: {0:yyyyMMddHHmmss} Username : {1}\{2} Machine : {3} ({4}) @@ -148,7 +148,7 @@ Machine : {3} ({4}) ********************** -PowerShell Core transcript end +PowerShell transcript end End time: {0:yyyyMMddHHmmss} ********************** @@ -156,7 +156,7 @@ End time: {0:yyyyMMddHHmmss} An instance of the ConsoleHost class has already been created for this process. - Command '{0}' could not be run because some PowerShell Core Snap-Ins did not load. + Command '{0}' could not be run because some PowerShell Snap-Ins did not load. Command '{0}' was not run as the session in which it was intended to run was either closed or broken diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostUserInterfaceStrings.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostUserInterfaceStrings.resx index ea616fe7807..f1f62ce4b2b 100644 --- a/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostUserInterfaceStrings.resx +++ b/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostUserInterfaceStrings.resx @@ -190,6 +190,6 @@ WARNING: {0} - PowerShell Core is in NonInteractive mode. Read and Prompt functionality is not available. + PowerShell is in NonInteractive mode. Read and Prompt functionality is not available. diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/HostMshSnapinResources.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/HostMshSnapinResources.resx index 2ddfb3f2bd6..7cfdd2f63b5 100644 --- a/src/Microsoft.PowerShell.ConsoleHost/resources/HostMshSnapinResources.resx +++ b/src/Microsoft.PowerShell.ConsoleHost/resources/HostMshSnapinResources.resx @@ -118,12 +118,12 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - This PowerShell Core snap-in contains cmdlets (such as Start-Transcript and Stop-Transcript) that are provided for use with the PowerShell Core console host. + This PowerShell snap-in contains cmdlets (such as Start-Transcript and Stop-Transcript) that are provided for use with the PowerShell console host. Microsoft Corporation - Host PowerShell Core Snap-In. + Host PowerShell Snap-In. diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/ManagedEntranceStrings.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/ManagedEntranceStrings.resx index 3918abaf1b8..912656e069d 100644 --- a/src/Microsoft.PowerShell.ConsoleHost/resources/ManagedEntranceStrings.resx +++ b/src/Microsoft.PowerShell.ConsoleHost/resources/ManagedEntranceStrings.resx @@ -134,11 +134,11 @@ Copyright (C) Microsoft Corporation. All rights reserved. PowerShell[.exe] -Help | -? | /? -PSConsoleFile - Loads the specified PowerShell Core console file. To create a console - file, use Export-Console in PowerShell Core. + Loads the specified PowerShell console file. To create a console + file, use Export-Console in PowerShell. -Version - Starts the specified version of PowerShell Core. + Starts the specified version of PowerShell. Enter a version number with the parameter, such as "-version 2.0". -NoLogo @@ -155,7 +155,7 @@ PowerShell[.exe] -Help | -? | /? Start the shell using a multithreaded apartment. -NoProfile - Does not load the PowerShell Core profile. + Does not load the PowerShell profile. -NonInteractive Does not present an interactive prompt to the user. @@ -164,11 +164,11 @@ PowerShell[.exe] -Help | -? | /? Present an interactive prompt to the user. -InputFormat - Describes the format of data sent to PowerShell Core. Valid values are + Describes the format of data sent to PowerShell. Valid values are "Text" (text strings) or "XML" (serialized CLIXML format). -OutputFormat - Determines how output from PowerShell Core is formatted. Valid values + Determines how output from PowerShell is formatted. Valid values are "Text" (text strings) or "XML" (serialized CLIXML format). -WindowStyle @@ -176,13 +176,13 @@ PowerShell[.exe] -Help | -? | /? -EncodedCommand Accepts a base-64-encoded string version of a command. Use this parameter - to submit commands to PowerShell Core that require complex quotation + to submit commands to PowerShell that require complex quotation marks or curly braces. -ConfigurationName - Specifies a configuration endpoint in which PowerShell Core is run. + Specifies a configuration endpoint in which PowerShell is run. This can be any endpoint registered on the local machine including the - default PowerShell Core remoting endpoints or a custom endpoint having + default PowerShell remoting endpoints or a custom endpoint having specific user role capabilities. -File @@ -196,12 +196,12 @@ PowerShell[.exe] -Help | -? | /? -ExecutionPolicy Sets the default execution policy for the current session and saves it in the $env:PSExecutionPolicyPreference environment variable. - This parameter does not change the PowerShell Core execution policy + This parameter does not change the PowerShell execution policy that is set in the registry. -Command Executes the specified commands (and any parameters) as though they were - typed at the PowerShell Core command prompt, and then exits, unless + typed at the PowerShell command prompt, and then exits, unless NoExit is specified. The value of Command can be "-", a string. or a script block. @@ -210,14 +210,14 @@ PowerShell[.exe] -Help | -? | /? If the value of Command is a script block, the script block must be enclosed in braces ({}). You can specify a script block only when running PowerShell.exe - in PowerShell Core. The results of the script block are returned to the + in PowerShell. The results of the script block are returned to the parent shell as deserialized XML objects, not live objects. If the value of Command is a string, Command must be the last parameter in the command , because any characters typed after the command are interpreted as the command arguments. - To write a string that runs a PowerShell Core command, use the format: + To write a string that runs a PowerShell command, use the format: "& {<command>}" where the quotation marks indicate a string and the invoke operator (&) causes the command to be executed. diff --git a/src/Microsoft.PowerShell.ScheduledJob/resources/ScheduledJobErrorStrings.resx b/src/Microsoft.PowerShell.ScheduledJob/resources/ScheduledJobErrorStrings.resx index 18af6ed3205..56ea7888180 100644 --- a/src/Microsoft.PowerShell.ScheduledJob/resources/ScheduledJobErrorStrings.resx +++ b/src/Microsoft.PowerShell.ScheduledJob/resources/ScheduledJobErrorStrings.resx @@ -134,7 +134,7 @@ There is no entry in Task Scheduler for scheduled job definition {0}. A new Task Scheduler entry has been created for this scheduled job definition. - Cannot get the {0} scheduled job because it is corrupted or in an irresolvable state. Because it cannot run, PowerShell Core has deleted {0} and its results from the computer. To recreate the scheduled job, use the Register-ScheduledJob cmdlet. For more information about corrupted scheduled jobs, see about_Scheduled_Jobs_Troubleshooting. + Cannot get the {0} scheduled job because it is corrupted or in an irresolvable state. Because it cannot run, PowerShell has deleted {0} and its results from the computer. To recreate the scheduled job, use the Register-ScheduledJob cmdlet. For more information about corrupted scheduled jobs, see about_Scheduled_Jobs_Troubleshooting. {0} is the name of the scheduled job definition. @@ -192,7 +192,7 @@ Scheduled job definition {0}. - A directory not found error occurred while registering scheduled job definition {0}. Make sure you are running PowerShell Core with elevated privileges. + A directory not found error occurred while registering scheduled job definition {0}. Make sure you are running PowerShell with elevated privileges. An error occurred while registering scheduled job definition {0}. Cannot add this definition object to the job store. @@ -231,7 +231,7 @@ The FilePath parameter is not valid. - Only PowerShell Core script files are allowed for FilePath parameter. Specify a file with .ps1 extension. + Only PowerShell script files are allowed for FilePath parameter. Specify a file with .ps1 extension. The IdleDuration parameter cannot have a negative value. @@ -255,7 +255,7 @@ The WeeksInterval parameter value must be greater than zero. - An I/O failure occurred while updating the scheduled job definition {0}. This could mean a file is missing or corrupted, either in Task Scheduler or in the PowerShell Core scheduled job store. You might need to create the scheduled job definition again. + An I/O failure occurred while updating the scheduled job definition {0}. This could mean a file is missing or corrupted, either in Task Scheduler or in the PowerShell scheduled job store. You might need to create the scheduled job definition again. {0} is the scheduled job definition name @@ -283,7 +283,7 @@ No Frequency type has been specified for this job trigger. One of the following job trigger frequencies must be specified: AtStartup, AtLogon, Once, Daily, Weekly. - An access denied error occurred while updating the scheduled job definition {0}. Try running PowerShell Core with elevated user rights; that is, Run as Administrator. + An access denied error occurred while updating the scheduled job definition {0}. Try running PowerShell with elevated user rights; that is, Run as Administrator. {0} is the scheduled job definition name @@ -320,7 +320,7 @@ Weekly - An access denied error occurred when registering scheduled job definition {0}. Try running PowerShell Core with elevated user rights; that is, Run As Administrator. + An access denied error occurred when registering scheduled job definition {0}. Try running PowerShell with elevated user rights; that is, Run As Administrator. Cannot convert a ScheduledJobTrigger object with TriggerFrequency value of {0}. @@ -334,7 +334,7 @@ {1} is the inner exception message from .Net serialization, or empty if no exception message. - Commands that interact with the host program, such as Write-Host, cannot be included in PowerShell Core scheduled jobs because scheduled jobs do not interact with the host program. Use an alternate command that does not interact with the host program, such as Write-Output or Out-File. + Commands that interact with the host program, such as Write-Host, cannot be included in PowerShell scheduled jobs because scheduled jobs do not interact with the host program. Use an alternate command that does not interact with the host program, such as Write-Output or Out-File. The RepetitionInterval parameter value must be less than or equal to the RepetitionDuration parameter value. diff --git a/src/Microsoft.PowerShell.Security/resources/CertificateProviderStrings.resx b/src/Microsoft.PowerShell.Security/resources/CertificateProviderStrings.resx index 5fd3f6b25d0..7884140dd38 100644 --- a/src/Microsoft.PowerShell.Security/resources/CertificateProviderStrings.resx +++ b/src/Microsoft.PowerShell.Security/resources/CertificateProviderStrings.resx @@ -187,6 +187,6 @@ The operation is on user root store and UI is not allowed. - . The following error may be a result of user credentials required on the remote machine. See Enable-WSManCredSSP Cmdlet help on how to enable and use CredSSP for delegation with PowerShell Core remoting. + . The following error may be a result of user credentials required on the remote machine. See Enable-WSManCredSSP Cmdlet help on how to enable and use CredSSP for delegation with PowerShell remoting. diff --git a/src/Microsoft.PowerShell.Security/resources/ExecutionPolicyCommands.resx b/src/Microsoft.PowerShell.Security/resources/ExecutionPolicyCommands.resx index ab053916583..0abbc073adc 100644 --- a/src/Microsoft.PowerShell.Security/resources/ExecutionPolicyCommands.resx +++ b/src/Microsoft.PowerShell.Security/resources/ExecutionPolicyCommands.resx @@ -118,7 +118,7 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - PowerShell Core updated your execution policy successfully, but the setting is overridden by a policy defined at a more specific scope. Due to the override, your shell will retain its current effective execution policy of {0}. Type "Get-ExecutionPolicy -List" to view your execution policy settings. For more information please see "Get-Help Set-ExecutionPolicy". + PowerShell updated your execution policy successfully, but the setting is overridden by a policy defined at a more specific scope. Due to the override, your shell will retain its current effective execution policy of {0}. Type "Get-ExecutionPolicy -List" to view your execution policy settings. For more information please see "Get-Help Set-ExecutionPolicy". Contact your system administrator. @@ -136,6 +136,6 @@ The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose you to the security risks described in the about_Execution_Policies help topic at https://go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy? - {0} To change the execution policy for the default (LocalMachine) scope, start PowerShell Core with the "Run as administrator" option. To change the execution policy for the current user, run "Set-ExecutionPolicy -Scope CurrentUser". + {0} To change the execution policy for the default (LocalMachine) scope, start PowerShell with the "Run as administrator" option. To change the execution policy for the current user, run "Set-ExecutionPolicy -Scope CurrentUser". diff --git a/src/Microsoft.PowerShell.Security/resources/SecurityMshSnapinResources.resx b/src/Microsoft.PowerShell.Security/resources/SecurityMshSnapinResources.resx index fbe8e61c921..e86df194720 100644 --- a/src/Microsoft.PowerShell.Security/resources/SecurityMshSnapinResources.resx +++ b/src/Microsoft.PowerShell.Security/resources/SecurityMshSnapinResources.resx @@ -118,12 +118,12 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - This PowerShell Core Snap-In contains cmdlets to manage PowerShell Core security. + This PowerShell Snap-In contains cmdlets to manage PowerShell security. Microsoft Corporation - Security PowerShell Core Snap-In. + Security PowerShell Snap-In. diff --git a/src/Microsoft.PowerShell.Security/resources/UtilsStrings.resx b/src/Microsoft.PowerShell.Security/resources/UtilsStrings.resx index e2a1882fb99..b067e9dc988 100644 --- a/src/Microsoft.PowerShell.Security/resources/UtilsStrings.resx +++ b/src/Microsoft.PowerShell.Security/resources/UtilsStrings.resx @@ -151,7 +151,7 @@ Central Access Policy identifier or name is not valid. If specifying an identifier, it must begin with S-1-17. If specifying a name, the policy must be applied on the target machine. - PowerShell Core credential request + PowerShell credential request Enter your credentials. diff --git a/src/Microsoft.WSMan.Management/resources/WsManResources.resx b/src/Microsoft.WSMan.Management/resources/WsManResources.resx index 6aacf3ac850..c55aab1132f 100644 --- a/src/Microsoft.WSMan.Management/resources/WsManResources.resx +++ b/src/Microsoft.WSMan.Management/resources/WsManResources.resx @@ -308,7 +308,7 @@ Do you want to continue? This command cannot be used from the current path. Move to root path of the provider using cd\ and run your command again. - This PowerShell Core snap-in contains cmdlets (such as Get-WSManInstance and Set-WSManInstance) that are used by the PowerShell Core host to manage WSMan operations. + This PowerShell snap-in contains cmdlets (such as Get-WSManInstance and Set-WSManInstance) that are used by the PowerShell host to manage WSMan operations. This command cannot be used to remove the computer 'localhost' because it will always be connected. Give some other connected computer and run your command. diff --git a/src/System.Management.Automation/resources/AutomationExceptions.resx b/src/System.Management.Automation/resources/AutomationExceptions.resx index 02c70aa8d38..eddbd1c9202 100644 --- a/src/System.Management.Automation/resources/AutomationExceptions.resx +++ b/src/System.Management.Automation/resources/AutomationExceptions.resx @@ -157,31 +157,31 @@ A script block that contains a top-level trap statement cannot be converted. - Cannot generate a PowerShell Core object for a ScriptBlock dereferencing variables undeclared in the param(...) block. Name of undeclared variable: {0}. + Cannot generate a PowerShell object for a ScriptBlock dereferencing variables undeclared in the param(...) block. Name of undeclared variable: {0}. - Cannot generate a PowerShell Core object for a ScriptBlock evaluating non-constant expressions. Non-constant expression: {0}. + Cannot generate a PowerShell object for a ScriptBlock evaluating non-constant expressions. Non-constant expression: {0}. - Cannot generate a PowerShell Core object for a ScriptBlock evaluating dynamic expressions. Dynamic expression: {0}. + Cannot generate a PowerShell object for a ScriptBlock evaluating dynamic expressions. Dynamic expression: {0}. - Cannot generate a PowerShell Core object for a ScriptBlock that tries to pass other script blocks inside argument values. + Cannot generate a PowerShell object for a ScriptBlock that tries to pass other script blocks inside argument values. - Cannot generate a PowerShell Core object for a ScriptBlock which invokes pipelines, commands or functions to evaluate arguments of the main pipeline. + Cannot generate a PowerShell object for a ScriptBlock which invokes pipelines, commands or functions to evaluate arguments of the main pipeline. - Cannot generate a PowerShell Core object for a ScriptBlock that uses dot sourcing. + Cannot generate a PowerShell object for a ScriptBlock that uses dot sourcing. - Cannot generate a PowerShell Core object for a ScriptBlock that invokes other script blocks. + Cannot generate a PowerShell object for a ScriptBlock that invokes other script blocks. - The script block cannot be converted to a PowerShell Core object because it contains forbidden redirection operators. + The script block cannot be converted to a PowerShell object because it contains forbidden redirection operators. - Cannot generate a PowerShell Core object for a ScriptBlock that does not have an associated operation context. + Cannot generate a PowerShell object for a ScriptBlock that does not have an associated operation context. The command was stopped by the user. @@ -193,7 +193,7 @@ The script block cannot be converted to an open generic type. Define an appropriate closed generic type, and then retry. - Cannot generate a PowerShell Core object for a ScriptBlock that starts a pipeline with an expression. + Cannot generate a PowerShell object for a ScriptBlock that starts a pipeline with an expression. Cannot create workflow. The type '{0}' from the '{1}' module could not be loaded. diff --git a/src/System.Management.Automation/resources/ConsoleInfoErrorStrings.resx b/src/System.Management.Automation/resources/ConsoleInfoErrorStrings.resx index bdc951d0bd7..201dde0e4ac 100644 --- a/src/System.Management.Automation/resources/ConsoleInfoErrorStrings.resx +++ b/src/System.Management.Automation/resources/ConsoleInfoErrorStrings.resx @@ -133,7 +133,7 @@ The console file is not valid because the element {0} is not valid. - The console file is not valid because the PowerShell Core snap-in name is missing. + The console file is not valid because the PowerShell snap-in name is missing. Attempting to save a console file with no name. Use Export-Console with the Path parameter to save the console file. @@ -151,49 +151,49 @@ The console file name extension is not valid. A console file name extension must be psc1. - Incorrect PowerShell Core version {0}. PowerShell Core version {1} is supported on this computer. + Incorrect PowerShell version {0}. PowerShell version {1} is supported on this computer. - Cannot find any PowerShell Core snap-in information for {0}. + Cannot find any PowerShell snap-in information for {0}. - This is a system PowerShell Core snap-in that is loaded by PowerShell Core. + This is a system PowerShell snap-in that is loaded by PowerShell. - Cannot add PowerShell Core snap-in {0} because it is already added. Verify the name of the snap-in, and then try again. + Cannot add PowerShell snap-in {0} because it is already added. Verify the name of the snap-in, and then try again. - Cannot remove the PowerShell Core snap-in {0} because it is not loaded. Verify the name of the snap-in that you want to remove, and then try again. + Cannot remove the PowerShell snap-in {0} because it is not loaded. Verify the name of the snap-in that you want to remove, and then try again. - Cannot remove the PowerShell Core snap-in {0} because it is a system snap-in. Verify the name of the snap-in that you want to remove, and then try again. + Cannot remove the PowerShell snap-in {0} because it is a system snap-in. Verify the name of the snap-in that you want to remove, and then try again. - Cannot load the PowerShell Core snap-in because an error occurred while reading the registry information for the snap-in. + Cannot load the PowerShell snap-in because an error occurred while reading the registry information for the snap-in. - An error occurred while attempting to load the system PowerShell Core snap-ins. Please contact Microsoft Customer Support Services. + An error occurred while attempting to load the system PowerShell snap-ins. Please contact Microsoft Customer Support Services. The following errors occurred when loading console {0}: {1} - Cannot load PowerShell Core snap-in {0} because of the following error: {1} + Cannot load PowerShell snap-in {0} because of the following error: {1} - PowerShell Core snap-in "{0}" loaded with the following warnings: {1} + PowerShell snap-in "{0}" loaded with the following warnings: {1} - The PowerShell Core snap-in module {0} does not have the required PowerShell Core snap-in strong name {1}. + The PowerShell snap-in module {0} does not have the required PowerShell snap-in strong name {1}. - The cmdlet '{0}' should not occur more than once in PowerShell Core snap-in '{1}'. + The cmdlet '{0}' should not occur more than once in PowerShell snap-in '{1}'. - PowerShell Core provider '{0}' should not occur more than once in PowerShell Core snap-in '{1}'. + PowerShell provider '{0}' should not occur more than once in PowerShell snap-in '{1}'. - PowerShell Core {0} is not supported in the current console. PowerShell Core {1} is supported in the current console. + PowerShell {0} is not supported in the current console. PowerShell {1} is supported in the current console. The cmdlet is not supported by the custom shell. diff --git a/src/System.Management.Automation/resources/CoreMshSnapinResources.resx b/src/System.Management.Automation/resources/CoreMshSnapinResources.resx index 9861a3cad99..39cb1e1b628 100644 --- a/src/System.Management.Automation/resources/CoreMshSnapinResources.resx +++ b/src/System.Management.Automation/resources/CoreMshSnapinResources.resx @@ -118,12 +118,12 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - This PowerShell Core snap-in contains cmdlets used to manage components of PowerShell Core. + This PowerShell snap-in contains cmdlets used to manage components of PowerShell. Microsoft Corporation - Core PowerShell Core snap-in + Core PowerShell snap-in diff --git a/src/System.Management.Automation/resources/CredUI.resx b/src/System.Management.Automation/resources/CredUI.resx index 69f17a3ce80..dee868450e9 100644 --- a/src/System.Management.Automation/resources/CredUI.resx +++ b/src/System.Management.Automation/resources/CredUI.resx @@ -118,7 +118,7 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - PowerShell Core credential request + PowerShell credential request Enter your credentials. diff --git a/src/System.Management.Automation/resources/CredentialAttributeStrings.resx b/src/System.Management.Automation/resources/CredentialAttributeStrings.resx index 67e3509f1ec..f496d90c988 100644 --- a/src/System.Management.Automation/resources/CredentialAttributeStrings.resx +++ b/src/System.Management.Automation/resources/CredentialAttributeStrings.resx @@ -118,7 +118,7 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - PowerShell Core credential request + PowerShell credential request Enter your credentials. diff --git a/src/System.Management.Automation/resources/DiscoveryExceptions.resx b/src/System.Management.Automation/resources/DiscoveryExceptions.resx index 618734d2d2a..cad3084524b 100644 --- a/src/System.Management.Automation/resources/DiscoveryExceptions.resx +++ b/src/System.Management.Automation/resources/DiscoveryExceptions.resx @@ -182,7 +182,7 @@ The #requires statement must be in one of the following formats: The script '{0}' cannot be run because it contained a "#requires" statement with a shell ID of {1} that is incompatible with the current shell. - The script '{0}' cannot be run because it contained a "#requires" statement for PowerShell Core {1}. The version of PowerShell Core that is required by the script does not match the currently running version of PowerShell Core {2}. + The script '{0}' cannot be run because it contained a "#requires" statement for PowerShell {1}. The version of PowerShell that is required by the script does not match the currently running version of PowerShell {2}. The script '{0}' cannot be run because it contained a "#requires" statement for PowerShell editions '{1}'. The edition of PowerShell that is required by the script does not match the currently running PowerShell {2} edition. @@ -191,10 +191,10 @@ The #requires statement must be in one of the following formats: The script '{0}' cannot be run because the following snap-ins that are specified by the "#requires" statements of the script are missing: {1}. - A #requires statement has specified only a shellID. #Requires statements must specify a required PowerShell Core snap-in when running in PowerShell Core. + A #requires statement has specified only a shellID. #Requires statements must specify a required PowerShell snap-in when running in PowerShell. - The script '{0}' cannot be run because it contains a "#requires" statement for running as Administrator. The current PowerShell Core session is not running as Administrator. Start PowerShell Core by using the Run as Administrator option, and then try running the script again. + The script '{0}' cannot be run because it contains a "#requires" statement for running as Administrator. The current PowerShell session is not running as Administrator. Start PowerShell by using the Run as Administrator option, and then try running the script again. {0} (Version {1}) diff --git a/src/System.Management.Automation/resources/EventingResources.resx b/src/System.Management.Automation/resources/EventingResources.resx index fa8eb9c177d..a501972cf60 100644 --- a/src/System.Management.Automation/resources/EventingResources.resx +++ b/src/System.Management.Automation/resources/EventingResources.resx @@ -124,10 +124,10 @@ Cannot register for the specified event. An event with the name '{0}' does not exist. - PowerShell Core cannot subscribe to Windows RT events. + PowerShell cannot subscribe to Windows RT events. - Cannot register for the specified event. The event source identifier '{0}' is reserved for the PowerShell Core engine. + Cannot register for the specified event. The event source identifier '{0}' is reserved for the PowerShell engine. This operation is not supported on remote instances. diff --git a/src/System.Management.Automation/resources/HelpDisplayStrings.resx b/src/System.Management.Automation/resources/HelpDisplayStrings.resx index 32b15d4916f..195cd831da9 100644 --- a/src/System.Management.Automation/resources/HelpDisplayStrings.resx +++ b/src/System.Management.Automation/resources/HelpDisplayStrings.resx @@ -334,10 +334,10 @@ (All) - No PowerShell Core modules were found that match the following pattern: {0}. Verify the pattern and then try the command again. + No PowerShell modules were found that match the following pattern: {0}. Verify the pattern and then try the command again. - No PowerShell Core modules were found that match the specified FullyQualifiedModule {0}. Verify the FullyQualifiedModule value and then try the command again. + No PowerShell modules were found that match the specified FullyQualifiedModule {0}. Verify the FullyQualifiedModule value and then try the command again. Help content cannot be found. Make sure the server is available and the help content location is properly defined in the HelpInfo XML. @@ -466,7 +466,7 @@ To update help again, add the Force parameter to your command. The root level element of the help content must be "helpItems". - The Update-Help cmdlet downloads the most current Help files for PowerShell Core modules, and installs them on your computer. For more information about the Update-Help cmdlet, see https://go.microsoft.com/fwlink/?LinkId=210614. + The Update-Help cmdlet downloads the most current Help files for PowerShell modules, and installs them on your computer. For more information about the Update-Help cmdlet, see https://go.microsoft.com/fwlink/?LinkId=210614. Do you want to run Update-Help? diff --git a/src/System.Management.Automation/resources/HelpErrors.resx b/src/System.Management.Automation/resources/HelpErrors.resx index d719e2242f6..9e1a3d8d1b0 100644 --- a/src/System.Management.Automation/resources/HelpErrors.resx +++ b/src/System.Management.Automation/resources/HelpErrors.resx @@ -175,7 +175,7 @@ Cannot get Help from a remote runspace, because the runspace has not been opened. Open the runspace by running an implicit remoting command, and then try running the command to get Help again. - Access is denied. The command could not update Help topics for the PowerShell Core core modules, or for any modules in the $pshome\Modules directory. To update these Help topics, start PowerShell Core by using the "Run as Administrator" command, and try running Update-Help again. + Access is denied. The command could not update Help topics for the PowerShell core modules, or for any modules in the $pshome\Modules directory. To update these Help topics, start PowerShell by using the "Run as Administrator" command, and try running Update-Help again. To use the {0}, install Windows PowerShell ISE by using Server Manager, and then restart this application. ({1}) diff --git a/src/System.Management.Automation/resources/HostInterfaceExceptionsStrings.resx b/src/System.Management.Automation/resources/HostInterfaceExceptionsStrings.resx index 8fdbdaa08a3..7ad809008c9 100644 --- a/src/System.Management.Automation/resources/HostInterfaceExceptionsStrings.resx +++ b/src/System.Management.Automation/resources/HostInterfaceExceptionsStrings.resx @@ -121,7 +121,7 @@ An error of type "{0}" has occurred. - A command that prompts the user failed because the host program or the command type does not support user interaction. Try a host program that supports user interaction, such as the PowerShell Core Console, and remove prompt-related commands from command types that do not support user interaction, such as PowerShell Core workflows. + A command that prompts the user failed because the host program or the command type does not support user interaction. Try a host program that supports user interaction, such as the PowerShell Console, and remove prompt-related commands from command types that do not support user interaction, such as PowerShell workflows. A command that prompts the user failed because the host program or the command type does not support user interaction. The host was attempting to request confirmation with the following message: {0} diff --git a/src/System.Management.Automation/resources/InternalHostUserInterfaceStrings.resx b/src/System.Management.Automation/resources/InternalHostUserInterfaceStrings.resx index a110f1ef05b..b55e117bac8 100644 --- a/src/System.Management.Automation/resources/InternalHostUserInterfaceStrings.resx +++ b/src/System.Management.Automation/resources/InternalHostUserInterfaceStrings.resx @@ -197,7 +197,7 @@ ********************** -PowerShell Core transcript start +PowerShell transcript start Start time: {0:yyyyMMddHHmmss} Username: {1} RunAs User: {2} @@ -210,7 +210,7 @@ Process ID: {7} ********************** -PowerShell Core transcript end +PowerShell transcript end End time: {0:yyyyMMddHHmmss} ********************** diff --git a/src/System.Management.Automation/resources/Metadata.resx b/src/System.Management.Automation/resources/Metadata.resx index 14fd34fa551..f4ce375cfea 100644 --- a/src/System.Management.Automation/resources/Metadata.resx +++ b/src/System.Management.Automation/resources/Metadata.resx @@ -223,7 +223,7 @@ The "{1}" validation script for the argument with value "{0}" did not return a result of True. Determine why the validation script failed, and then try the command again. - The "{0}" argument does not contain a valid PowerShell Core version. Supply a valid version number and then try the command again. + The "{0}" argument does not contain a valid PowerShell version. Supply a valid version number and then try the command again. Cannot validate argument '{0}' because it is not a valid variable name. diff --git a/src/System.Management.Automation/resources/Modules.resx b/src/System.Management.Automation/resources/Modules.resx index ebf534444d8..c46d41e3c11 100644 --- a/src/System.Management.Automation/resources/Modules.resx +++ b/src/System.Management.Automation/resources/Modules.resx @@ -157,7 +157,7 @@ The module manifest '{0}' could not be processed because it is not a valid PowerShell module manifest file. Remove the elements that are not permitted: {1} - Processing the module manifest file '{0}' did not result in a valid manifest object. Update the file to contain a valid PowerShell Core module manifest. A valid manifest can be created using the New-ModuleManifest cmdlet. + Processing the module manifest file '{0}' did not result in a valid manifest object. Update the file to contain a valid PowerShell module manifest. A valid manifest can be created using the New-ModuleManifest cmdlet. The '{0}' module cannot be imported because its manifest contains one or more members that are not valid. The valid manifest members are ({1}). Remove the members that are not valid ({2}), then try to import the module again. @@ -181,7 +181,7 @@ The version of the Common Language Runtime (CLR) on this computer is '{0}'. The module '{1}' requires a minimum CLR version of '{2}' to run. Verify that you are running the minimum required version of CLR, and then try again. - The version of PowerShell Core on this computer is '{0}'. The module '{1}' requires a minimum PowerShell Core version of '{2}' to run. Verify that you have the minimum required version of PowerShell Core installed, and then try again. + The version of PowerShell on this computer is '{0}'. The module '{1}' requires a minimum PowerShell version of '{2}' to run. Verify that you have the minimum required version of PowerShell installed, and then try again. The module manifest member 'NestedModules' cannot be used if the 'ModuleToProcess' member is a binary module. Edit the module manifest file at '{0}', and then try again. @@ -346,10 +346,10 @@ The module '{0}' requires the following version of the .NET Framework: {1}. The required version is not installed. - The name of the current PowerShell Core host is: '{0}'. The module '{1}' requires the following PowerShell Core host: '{2}'. + The name of the current PowerShell host is: '{0}'. The module '{1}' requires the following PowerShell host: '{2}'. - The current PowerShell Core host is: '{0}' (version {1}). The module '{2}' requires a minimum PowerShell Core host version of '{3}' to run. + The current PowerShell host is: '{0}' (version {1}). The module '{2}' requires a minimum PowerShell host version of '{3}' to run. Module manifest for module '{0}' @@ -388,7 +388,7 @@ Description of the functionality provided by this module - Minimum version of the PowerShell Core engine required by this module + Minimum version of the PowerShell engine required by this module Minimum version of the common language runtime (CLR) required by this module. {0} @@ -475,10 +475,10 @@ Minimum version of Microsoft .NET Framework required by this module. {0} - Name of the PowerShell Core host required by this module + Name of the PowerShell host required by this module - Minimum version of the PowerShell Core host required by this module + Minimum version of the PowerShell host required by this module Loading workflow {0} @@ -487,13 +487,13 @@ HelpInfo URI of this module - The item {0} that resolves to {1} is not located in the same directory as the module manifest or any of its subdirectories. PowerShell Core looks for items referenced in the manifest only in paths relative to the manifest location. To fix this problem, move the item, and use a relative path to identify its location. + The item {0} that resolves to {1} is not located in the same directory as the module manifest or any of its subdirectories. PowerShell looks for items referenced in the manifest only in paths relative to the manifest location. To fix this problem, move the item, and use a relative path to identify its location. The workflow file name is not valid because it does not have the required .XAML file name extension. Run the New-ModuleManifest command again specifying a value for the WorkflowsToProcess parameter with this extension. - Because the {0} module is providing the PSDrive in the current PowerShell Core session, no modules were removed. Change the current PSDrive provider, and then try removing modules again. + Because the {0} module is providing the PSDrive in the current PowerShell session, no modules were removed. Change the current PSDrive provider, and then try removing modules again. The workflow file name extension is not valid. The workflow file name {0} that is listed in the WorkflowsToProcess key of the module manifest does not have the required .XAML or .DLL file name extension. Edit the module manifest and correct the workflow file name. If you are using a .DLL file extension, then provide only one assembly name. @@ -514,7 +514,7 @@ Wildcard characters are not allowed in members 'ModuleToProcess', 'RootModule', or 'NestedModules' in the module manifest '{0}'. - The module '{0}' is a core module for PowerShell Core. Add the Force parameter to your command to remove core modules. + The module '{0}' is a core module for PowerShell. Add the Force parameter to your command to remove core modules. The module manifest cannot contain both the 'ModuleToProcess' and 'RootModule' members. Change the module manifest file to remove one of these members at '{0}', and then try again. @@ -535,7 +535,7 @@ The required module '{0}' was not loaded because no valid module file was found in any module directory. - Some commands from module {0} cannot be imported over a CimSession. To get all the commands, verify that the remote server has PowerShell Core remote management enabled, and then try adding the PSSession parameter to an Import-Module cmdlet. + Some commands from module {0} cannot be imported over a CimSession. To get all the commands, verify that the remote server has PowerShell remote management enabled, and then try adding the PSSession parameter to an Import-Module cmdlet. The module {0} cannot be imported over a CimSession. Try using the PSSession parameter of the Import-Module cmdlet. @@ -625,7 +625,7 @@ The specified module '{0}' was not found. Update the Name parameter to point to a valid path, and then try again. - Cannot load the workflow module '{0}'. Workflow is not supported in PowerShell Core. + Cannot load the workflow module '{0}'. Workflow is not supported in PowerShell. Populating RepositorySourceLocation property for module {0}. diff --git a/src/System.Management.Automation/resources/MshSnapInCmdletResources.resx b/src/System.Management.Automation/resources/MshSnapInCmdletResources.resx index 7adcb713040..5535ffd850a 100644 --- a/src/System.Management.Automation/resources/MshSnapInCmdletResources.resx +++ b/src/System.Management.Automation/resources/MshSnapInCmdletResources.resx @@ -121,15 +121,15 @@ The operation cannot be performed. The specified cmdlet is not supported in a custom shell. - No PowerShell Core snap-ins matching the pattern '{0}' were found. Check the pattern and then try the command again. + No PowerShell snap-ins matching the pattern '{0}' were found. Check the pattern and then try the command again. - The format of the specified snap-in name was not valid. PowerShell Core snap-in names can only contain alpha-numeric characters, dashes, underscores and periods. Correct the name and then try the operation again. + The format of the specified snap-in name was not valid. PowerShell snap-in names can only contain alpha-numeric characters, dashes, underscores and periods. Correct the name and then try the operation again. - Cannot add PowerShell Core snap-in {0} because it is a system PowerShell Core module. Use Import-Module to load the module. + Cannot add PowerShell snap-in {0} because it is a system PowerShell module. Use Import-Module to load the module. - The custom PowerShell Core snap-in is not supported in PowerShell Core. + The custom PowerShell snap-in is not supported in PowerShell. diff --git a/src/System.Management.Automation/resources/MshSnapinInfo.resx b/src/System.Management.Automation/resources/MshSnapinInfo.resx index 93fbed47508..874fe8a9930 100644 --- a/src/System.Management.Automation/resources/MshSnapinInfo.resx +++ b/src/System.Management.Automation/resources/MshSnapinInfo.resx @@ -118,19 +118,19 @@ System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - Unable to access PowerShell Core registry information. + Unable to access PowerShell registry information. - Unable to access PowerShell Core PowerShellEngine registry information. + Unable to access PowerShell PowerShellEngine registry information. Unable to access PublicKeyToken information. - Version {0} of PowerShell Core is not available on this computer. + Version {0} of PowerShell is not available on this computer. - The PowerShell Core snap-in '{0}' is not installed on this computer. + The PowerShell snap-in '{0}' is not installed on this computer. The mandatory value {0} is not specified for registry key {1}. @@ -145,7 +145,7 @@ Cannot find required information in registry or missing key files. Cannot load some cmdlets. - No snap-ins have been registered for PowerShell Core version {0}. + No snap-ins have been registered for PowerShell version {0}. Cannot retrieve the string resource because the reader has been disposed. @@ -154,6 +154,6 @@ Version value {0} is not specified or is incorrect for registry key {1}. - No [PSVersion] attribute was found for PowerShell Core type {0}. Add a PSVersion attribute to the type using [PSVersion(PowerShell Core SnapinBase.PSEngineVersion)]. + No [PSVersion] attribute was found for PowerShell type {0}. Add a PSVersion attribute to the type using [PSVersion(PowerShell SnapinBase.PSEngineVersion)]. diff --git a/src/System.Management.Automation/resources/ParserStrings.resx b/src/System.Management.Automation/resources/ParserStrings.resx index 028de2d3dca..3c19d7387ec 100644 --- a/src/System.Management.Automation/resources/ParserStrings.resx +++ b/src/System.Management.Automation/resources/ParserStrings.resx @@ -850,7 +850,7 @@ Possible matches are Flow of control cannot leave a Finally block. - Unrecoverable error in PowerShell Core. + Unrecoverable error in PowerShell. An AST cannot be used as the child of more than one AST. To use this AST in another AST, call the Copy() method and use its result. @@ -925,7 +925,7 @@ Possible matches are The argument for the Module parameter is not valid. {0} - The argument for the Version parameter is not valid. Specify a valid PowerShell Core version, in the format major.minor version. + The argument for the Version parameter is not valid. Specify a valid PowerShell version, in the format major.minor version. The argument for the {0} parameter is not valid. Specify a valid PowerShell edition. @@ -1192,7 +1192,7 @@ ModuleVersion : Version of module to import. If used, ModuleName must represent Exception occurred when post-parsing dynamic keyword '{0}' with details '{1}'. - Workflow is not supported in PowerShell Core. + Workflow is not supported in PowerShell. Meta Configuration resource {0} is not allowed in the regular configuration. Use meta configuration resources in a configuration with [DscLocalConfigurationManager()] attribute. @@ -1261,7 +1261,7 @@ ModuleVersion : Version of module to import. If used, ModuleName must represent Variant.GetAccessor cannot handle {0}. - Configuration keyword is not supported in PowerShell Core. + Configuration keyword is not supported in PowerShell. Not all code path returns value within method. @@ -1355,7 +1355,7 @@ ModuleVersion : Version of module to import. If used, ModuleName must represent '{1}'. - Cannot run a document in PowerShell Core: {0}. + Cannot run a document in PowerShell: {0}. Multiple type constraints are not allowed on a method parameter. diff --git a/src/System.Management.Automation/resources/PowerShellStrings.resx b/src/System.Management.Automation/resources/PowerShellStrings.resx index a6e54f9ee34..0fafa86a13d 100644 --- a/src/System.Management.Automation/resources/PowerShellStrings.resx +++ b/src/System.Management.Automation/resources/PowerShellStrings.resx @@ -142,7 +142,7 @@ Nested PowerShell instances cannot be invoked asynchronously. Use the Invoke method. - The {0} object was not created by calling {1} on this PowerShell Core instance. + The {0} object was not created by calling {1} on this PowerShell instance. When the runspace is set to reuse a thread, the apartment state in the invocation settings must match the runspace. @@ -151,7 +151,7 @@ When the runspace is set to use the current thread, the apartment state in the invocation settings must match that of the current thread. - A command is required to add a parameter. A command must be added to the PowerShell Core instance before adding a parameter. + A command is required to add a parameter. A command must be added to the PowerShell instance before adding a parameter. The keys in the dictionary must be strings. @@ -163,10 +163,10 @@ You can only begin receiving data on a PSJobProxy instance when it has been created with data streaming disabled. This operation can run only once. - GetJobForCommand is not supported when there is more than one command in the PowerShell Core instance. + GetJobForCommand is not supported when there is more than one command in the PowerShell instance. - The Command property of a PowerShell Core object cannot be empty. + The Command property of a PowerShell object cannot be empty. The PSJobProxy object can only be used for remote commands that return a job object. @@ -193,16 +193,16 @@ A job object cannot be reused. - This PowerShell Core object cannot be connected because it is not associated with a remote runspace or runspace pool. + This PowerShell object cannot be connected because it is not associated with a remote runspace or runspace pool. The running command has been disconnected but is still running on the remote server. Reconnect to get command operation status and output data. - The operation cannot be performed because the current PowerShell Core session is in the Disconnected state. Connect this PowerShell Core session, and then either wait for the command to finish, or stop the command. + The operation cannot be performed because the current PowerShell session is in the Disconnected state. Connect this PowerShell session, and then either wait for the command to finish, or stop the command. - The operation cannot be performed because the current PowerShell Core session is in the Disconnected state. Connect this PowerShell Core session, and then try again. + The operation cannot be performed because the current PowerShell session is in the Disconnected state. Connect this PowerShell session, and then try again. The connection attempt to the remote command failed. @@ -215,7 +215,7 @@ The operation cannot be performed because a command is currently stopping. Wait for the command to complete stopping, and then try the operation again. - There is no Runspace available to run commands in this thread. You can provide one in the DefaultRunspace property of the System.Management.Automation.Runspaces.Runspace type. The current PowerShell Core instance contains no command to invoke. + There is no Runspace available to run commands in this thread. You can provide one in the DefaultRunspace property of the System.Management.Automation.Runspaces.Runspace type. The current PowerShell instance contains no command to invoke. A command in which the value of AsJob is equal to false cannot be run through a PSJobProxy. @@ -226,7 +226,7 @@ PSJobProxy is the name of a class and should not be localized - A PowerShell Core object cannot be created that uses the current runspace because there is no current runspace available. The current runspace might be starting, such as when it is created with an Initial Session State. + A PowerShell object cannot be created that uses the current runspace because there is no current runspace available. The current runspace might be starting, such as when it is created with an Initial Session State. PSJobProxy does not support this control method. diff --git a/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx b/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx index 71eda94917d..7eb96d7d2f3 100644 --- a/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx +++ b/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx @@ -172,7 +172,7 @@ Only administrators can override the Thread Options remotely. - PowerShell Core Credential Request: {0} + PowerShell Credential Request: {0} Warning: A script or application on the remote computer {0} is requesting your credentials. Enter your credentials only if you trust the remote computer and the application or script that is requesting them. @@ -183,7 +183,7 @@ A script or application on the remote computer {0} is asking to read a line securely. Enter sensitive information, such as your credentials, only if you trust the remote computer and the application or script that is requesting it. - A script or application on the remote computer {0} is attempting to read the buffer contents on the PowerShell Core host. For security reasons, this is not allowed; the call has been suppressed. + A script or application on the remote computer {0} is attempting to read the buffer contents on the PowerShell host. For security reasons, this is not allowed; the call has been suppressed. A script or application on the remote computer {0} is sending a prompt request. When you are prompted, enter sensitive information, such as credentials or passwords, only if you trust the remote computer and the application or script that is requesting the data. @@ -270,7 +270,7 @@ Error in decoding Maximum runspaces. - Error in decoding PowerShell CoreStateInfo. + Error in decoding PowerShellStateInfo. Unexpected type of {0} property (expected {1}, got {2}). @@ -294,31 +294,31 @@ The client negotiation timer has expired. The negotiation time-out interval is {0} milliseconds. - PowerShell Core client does not support the {0} {1} negotiated by the server. Make sure the server is compatible with the build {2} and the protocol version {3} of PowerShell Core. + PowerShell client does not support the {0} {1} negotiated by the server. Make sure the server is compatible with the build {2} and the protocol version {3} of PowerShell. - {0}. Negotiation with the server failed. Make sure the server is compatible with the build {1} and the protocol version {2} of PowerShell Core. + {0}. Negotiation with the server failed. Make sure the server is compatible with the build {1} and the protocol version {2} of PowerShell. The destination server has sent a request to close the session. - The server that is running PowerShell Core does not support the {0} {1} negotiated by the client computer. Verify that the client computer is compatible with the build {2} and the protocol version {3} of PowerShell Core. + The server that is running PowerShell does not support the {0} {1} negotiated by the client computer. Verify that the client computer is compatible with the build {2} and the protocol version {3} of PowerShell. - The server that is running PowerShell Core does not support connect operations on the {0} {1} that is negotiated by the client computer. Make sure the client computer is compatible with the build {2} and the protocol version {3} of PowerShell Core. + The server that is running PowerShell does not support connect operations on the {0} {1} that is negotiated by the client computer. Make sure the client computer is compatible with the build {2} and the protocol version {3} of PowerShell. - The server that is running PowerShell Core cannot process the connect operation because the following information is not found or not valid: Client Capability information and Connect RunspacePool information. + The server that is running PowerShell cannot process the connect operation because the following information is not found or not valid: Client Capability information and Connect RunspacePool information. - The server that is running PowerShell Core cannot process the connect operation because the server has either not been started, or it is shutting down. + The server that is running PowerShell cannot process the connect operation because the server has either not been started, or it is shutting down. - The server that is running PowerShell Core cannot process the connect operation because the server runspace pool properties did not match the client computer specified properties. + The server that is running PowerShell cannot process the connect operation because the server runspace pool properties did not match the client computer specified properties. - {0}. Negotiation with the client failed. Make sure the client is compatible with the build {1} and the protocol version {2} of PowerShell Core. + {0}. Negotiation with the client failed. Make sure the client is compatible with the build {1} and the protocol version {2} of PowerShell. The server negotiation timer has expired. The negotiation time-out interval is {0} milliseconds. @@ -327,7 +327,7 @@ The client computer has sent a request to close the session. - An error has occurred which PowerShell Core cannot handle. A remote session might have ended. + An error has occurred which PowerShell cannot handle. A remote session might have ended. The server did not respond with an encrypted session key within the specified time-out period. @@ -342,7 +342,7 @@ Attempting to close the session. - PowerShell Core cannot close the remote session properly. The session is in an undefined state because it was not opened or connected after being disconnected. PowerShell Core will try to force the session to close on the local computer, but the session might not be closed on the remote computer. To close a remote session properly, first open it or connect it. + PowerShell cannot close the remote session properly. The session is in an undefined state because it was not opened or connected after being disconnected. PowerShell will try to force the session to close on the local computer, but the session might not be closed on the remote computer. To close a remote session properly, first open it or connect it. Could not close the session. @@ -459,10 +459,10 @@ Inter-process communication (IPC) transport does not support connect operations. - An EndpointConfiguration with Id {0} does not exist on the remote server. Contact your PowerShell Core administrator, or the owner or creator of the endpoint configuration. + An EndpointConfiguration with Id {0} does not exist on the remote server. Contact your PowerShell administrator, or the owner or creator of the endpoint configuration. - The EndpointConfiguration with the {0} identifier is not in a valid initial session state on the remote computer. Contact your PowerShell Core administrator, or the owner or creator of the endpoint configuration. + The EndpointConfiguration with the {0} identifier is not in a valid initial session state on the remote computer. Contact your PowerShell administrator, or the owner or creator of the endpoint configuration. The mandatory value {0} is not specified for the {1} registry key. @@ -471,7 +471,7 @@ The mandatory value {0} is not in the correct format for registry key {1}. The expected format is 'string'. - "{0}" must specify a PowerShell Core script file that ends with extension ".ps1". + "{0}" must specify a PowerShell script file that ends with extension ".ps1". The {0} parameter is already specified in the {1} section. Contact your administrator to make sure that {0} is specified only once. @@ -552,7 +552,7 @@ The path specified as the value of the FilePath parameter is not from the FileSystem provider. - The value of the FilePath parameter must be a PowerShell Core script file. Enter the path to a file with a .ps1 file name extension and try the command again. + The value of the FilePath parameter must be a PowerShell script file. Enter the path to a file with a .ps1 file name extension and try the command again. One or more computer names are not valid. If you are trying to pass a URI, use the -ConnectionUri parameter, or pass URI objects instead of strings. @@ -582,7 +582,7 @@ Remote Command: {0}, associated with a job that has an ID of "{1}". - The command cannot retrieve the jobs of the specified computers. The ComputerName parameter can be used only with jobs created by using PowerShell Core remoting. + The command cannot retrieve the jobs of the specified computers. The ComputerName parameter can be used only with jobs created by using PowerShell remoting. The Session parameter can be used only with PSRemotingJob objects. @@ -654,13 +654,13 @@ Session configuration "{0}" was not found. - Session configuration "{0}" is not a PowerShell Core-based shell. + Session configuration "{0}" is not a PowerShell-based shell. - Session configuration "{0}" is a PowerShell Core-based shell. Please use PowerShell Core to modify it. + Session configuration "{0}" is a PowerShell-based shell. Please use PowerShell to modify it. - Session configuration "{0}" is a PowerShell Core-based shell. Please use PowerShell Core to modify it. + Session configuration "{0}" is a PowerShell-based shell. Please use PowerShell to modify it. No session configuration matches criteria "{0}". @@ -672,13 +672,13 @@ Name: {0} - Name: {0}. This lets administrators remotely run PowerShell Core commands on this computer. + Name: {0}. This lets administrators remotely run PowerShell commands on this computer. Cannot delete temporary file {0}. Reason for failure: {1}. - The new shell was successfully registered, but PowerShell Core cannot delete the temporary file {0}. Reason for failure: {1}. + The new shell was successfully registered, but PowerShell cannot delete the temporary file {0}. Reason for failure: {1}. Cannot write the shell configuration data into the temporary file {0}. Reason for failure: {1}. @@ -687,13 +687,13 @@ Running command "{0}" to create a new session configuration. - Name: {0} SDDL: {1}. This lets selected users remotely run PowerShell Core commands on this computer. + Name: {0} SDDL: {1}. This lets selected users remotely run PowerShell commands on this computer. Running command "{0}" to remove a session configuration. - Running command "{0}" to get PowerShell Core-based session configurations. + Running command "{0}" to get PowerShell-based session configurations. Running command "{0}" to update the session configuration properties. @@ -721,7 +721,7 @@ Do you want to continue? Performing operation "{0}". - Name: {0} SDDL: {1}. This lets selected users remotely run PowerShell Core commands on this computer. + Name: {0} SDDL: {1}. This lets selected users remotely run PowerShell commands on this computer. Running command "{0}" to disable the session configuration. @@ -737,7 +737,7 @@ Do you want to continue? 4. Restore the value of the LocalAccountTokenFilterPolicy to 0, which restricts remote access to members of the Administrators group on the computer. - Access is denied. To run this cmdlet, start PowerShell Core with the "Run as administrator" option. + Access is denied. To run this cmdlet, start PowerShell with the "Run as administrator" option. Restarting WinRM service @@ -846,7 +846,7 @@ Do you want to continue? The WriteEvents parameter cannot be used without the Wait parameter. - PowerShell Core {0} is not installed. Install PowerShell Core {0}, and then try again. + PowerShell {0} is not installed. Install PowerShell {0}, and then try again. The following type cannot be instantiated because its constructor is not public: {0}. @@ -933,14 +933,14 @@ Do you want to continue? The command cannot find a PSSession that has the name "{0}". - PowerShell Core remoting is not supported in the Windows Preinstallation Environment (WinPE). + PowerShell remoting is not supported in the Windows Preinstallation Environment (WinPE). Changes made by {0} cannot take effect until the WinRM service is restarted. {0} may need to restart the WinRM service if a configuration using this name has recently been unregistered, certain system data structures may still be cached. In that case, a restart of WinRM may be required. -All WinRM sessions connected to PowerShell Core session configurations, such as Microsoft.PowerShell and session configurations that are created with the Register-PSSessionConfiguration cmdlet, are disconnected. +All WinRM sessions connected to PowerShell session configurations, such as Microsoft.PowerShell and session configurations that are created with the Register-PSSessionConfiguration cmdlet, are disconnected. You are running in a remote session and have selected the Force option which means the WinRM service may restart.If the WinRM service restarts then this remote session will be terminated and you will need to create a new session to continue @@ -952,7 +952,7 @@ All WinRM sessions connected to PowerShell Core session configurations, such as A running command could not be found for this PSSession. - The Microsoft .NET Framework 2.0, which is required for PowerShell Core 2.0, is not installed. Install the .NET Framework 2.0 and retry. + The Microsoft .NET Framework 2.0, which is required for PowerShell 2.0, is not installed. Install the .NET Framework 2.0 and retry. The remote pipeline failed. @@ -1030,7 +1030,7 @@ All WinRM sessions connected to PowerShell Core session configurations, such as Modules to import when applied to a session - Version of the PowerShell Core engine to use when applied to a session + Version of the PowerShell engine to use when applied to a session Processor architecture to use when applied to a session @@ -1196,7 +1196,7 @@ All WinRM sessions connected to PowerShell Core session configurations, such as The PSSession is in a disconnected state and is not available for connection. - The Hyper-V Module for PowerShell Core is not available on this machine. + The Hyper-V Module for PowerShell is not available on this machine. Failed to launch PowerShell process inside container with id {0}. @@ -1318,7 +1318,7 @@ All WinRM sessions connected to PowerShell Core session configurations, such as One or more jobs are in a suspended or disconnected state, and cannot continue without additional user input. Specify the -Force parameter to continue to a completed, failed, or stopped state. - When RunAs is enabled in a PowerShell Core session configuration, the Windows security model cannot enforce a security boundary between different user sessions that are created by using this endpoint. Verify that the PowerShell Core runspace configuration is restricted to only the necessary set of cmdlets and capabilities. + When RunAs is enabled in a PowerShell session configuration, the Windows security model cannot enforce a security boundary between different user sessions that are created by using this endpoint. Verify that the PowerShell runspace configuration is restricted to only the necessary set of cmdlets and capabilities. The job was suspended successfully by adding the Force parameter. @@ -1333,7 +1333,7 @@ All WinRM sessions connected to PowerShell Core session configurations, such as The workflow job "{0}" was stopped. Receive-Job is only displaying partial results. - Disconnected sessions are supported only when the remote computer is running PowerShell Core 3.0 or a later version of PowerShell Core. + Disconnected sessions are supported only when the remote computer is running PowerShell 3.0 or a later version of PowerShell. Memory usage of a cmdlet has exceeded a warning level. To avoid this situation, try one of the following: 1) Lower the rate at which CIM operations produce data (for example, by passing a low value to the ThrottleLimit parameter), 2) Increase the rate at which data is consumed by downstream cmdlets, or 3) Use the Invoke-Command cmdlet to run the whole pipeline on the server. The cmdlet that exceeded a warning level of memory usage was started by the following command line: {0} @@ -1342,7 +1342,7 @@ All WinRM sessions connected to PowerShell Core session configurations, such as PSSession {0} was created using the EnableNetworkAccess parameter and can only be reconnected from the local computer. - You are currently in a PowerShell Core PSSession and cannot use the Enter-PSSession cmdlet to enter another PSSession. + You are currently in a PowerShell PSSession and cannot use the Enter-PSSession cmdlet to enter another PSSession. Cannot start job. The language mode for this session is incompatible with the system-wide language mode. @@ -1354,7 +1354,7 @@ All WinRM sessions connected to PowerShell Core session configurations, such as Cannot exit a nested pipeline because the pipeline is not in the nested state. - The PowerShell Core server session is not in a valid state for running nested commands. No nested commands can be run in this session. + The PowerShell server session is not in a valid state for running nested commands. No nested commands can be run in this session. Cannot invoke a nested command on the remote session because a nested command is already running. @@ -1366,7 +1366,7 @@ All WinRM sessions connected to PowerShell Core session configurations, such as The remote session command is currently stopped in the debugger. Use the Enter-PSSession cmdlet to connect interactively to the remote session and automatically enter into the console debugger. - The remote session to which you are connected does not support remote debugging. You must connect to a remote computer that is running PowerShell Core {0} or greater. + The remote session to which you are connected does not support remote debugging. You must connect to a remote computer that is running PowerShell {0} or greater. Because the session state for session {0}, {1}, {2} is not equal to Open, you cannot run a command in the session. The session state is {3}. @@ -1408,13 +1408,13 @@ All WinRM sessions connected to PowerShell Core session configurations, such as The Named Pipe server listener used for process attach is already running. - Enter-PSHostProcess does not support entering the same PowerShell Core session it is running in. + Enter-PSHostProcess does not support entering the same PowerShell session it is running in. Multiple processes were found with this name {0}. Use the process Id to specify a single process to enter. - Cannot enter process {0} because it has not loaded the PowerShell Core engine. + Cannot enter process {0} because it has not loaded the PowerShell engine. No process was found with Id: {0}. @@ -1646,13 +1646,13 @@ All WinRM sessions connected to PowerShell Core session configurations, such as The SSH transport process has abruptly terminated causing this remote session to break. - PowerShell Core does not support WOW64. The binary must match the architecture of the processor. + PowerShell does not support WOW64. The binary must match the architecture of the processor. Unable to install plugin {0} to directory {1}. - The WinRM plugin DLL {0} is missing for PowerShell Core. Please run Enable-PSRemoting and then retry this command. + The WinRM plugin DLL {0} is missing for PowerShell. Please run Enable-PSRemoting and then retry this command. This parameter set requires WSMan, and no supported WSMan client library was found. WSMan is either not installed or unavailable for this system. diff --git a/src/System.Management.Automation/resources/RunspaceInit.resx b/src/System.Management.Automation/resources/RunspaceInit.resx index 18fc9989b89..b8aee86a251 100644 --- a/src/System.Management.Automation/resources/RunspaceInit.resx +++ b/src/System.Management.Automation/resources/RunspaceInit.resx @@ -130,7 +130,7 @@ The run objects available to cmdlets - Version information for current PowerShell Core session + Version information for current PowerShell session Current process ID @@ -199,10 +199,10 @@ Displays errors with a description of the error class - Culture of the current PowerShell Core session + Culture of the current PowerShell session - UI culture of the current PowerShell Core session + UI culture of the current PowerShell session Variable to hold all default <cmdlet:parameter, value> pairs diff --git a/src/System.Management.Automation/resources/RunspacePoolStrings.resx b/src/System.Management.Automation/resources/RunspacePoolStrings.resx index 5a2ae22b735..b6f7561247a 100644 --- a/src/System.Management.Automation/resources/RunspacePoolStrings.resx +++ b/src/System.Management.Automation/resources/RunspacePoolStrings.resx @@ -160,7 +160,7 @@ The Disconnect operation is not supported on the server. The server must be running Windows PowerShell 3.0 or greater for remote runspace pool disconnection support. - This runspace pool {0} is not configured to provide disconnected PowerShell Core objects for commands running on the remote server. Use the RunspacePool class GetRunspacePools() static method to query the server and return runspace pool objects that are configured to do this. + This runspace pool {0} is not configured to provide disconnected PowerShell objects for commands running on the remote server. Use the RunspacePool class GetRunspacePools() static method to query the server and return runspace pool objects that are configured to do this. This runspace pool cannot be connected because the corresponding server side runspace pool is connected to another client. diff --git a/src/System.Management.Automation/resources/RunspaceStrings.resx b/src/System.Management.Automation/resources/RunspaceStrings.resx index 377d38cd9af..81a34adc199 100644 --- a/src/System.Management.Automation/resources/RunspaceStrings.resx +++ b/src/System.Management.Automation/resources/RunspaceStrings.resx @@ -237,7 +237,7 @@ - You have entered a session that is currently stopped at a debug breakpoint inside a running command or script. Use the PowerShell Core command line debugger to continue debugging. + You have entered a session that is currently stopped at a debug breakpoint inside a running command or script. Use the PowerShell command line debugger to continue debugging. diff --git a/src/System.Management.Automation/resources/Serialization.resx b/src/System.Management.Automation/resources/Serialization.resx index ba7d2ed1ce5..3db94ff2b05 100644 --- a/src/System.Management.Automation/resources/Serialization.resx +++ b/src/System.Management.Automation/resources/Serialization.resx @@ -178,7 +178,7 @@ The key type {0} is not valid. The PSPrimitiveDictionary class accepts only keys of the type System.String. - The type of the value {0} is not valid. The PSPrimitiveDictionary class accepts only values of types that are fully serializable over PowerShell Core remoting. See the Help topic about_Remoting for a list of fully-serializable types. + The type of the value {0} is not valid. The PSPrimitiveDictionary class accepts only values of types that are fully serializable over PowerShell remoting. See the Help topic about_Remoting for a list of fully-serializable types. Could not decrypt data. The data was not encrypted with this key. diff --git a/src/System.Management.Automation/resources/SessionStateStrings.resx b/src/System.Management.Automation/resources/SessionStateStrings.resx index 9a2782e1d01..d7a7afcec70 100644 --- a/src/System.Management.Automation/resources/SessionStateStrings.resx +++ b/src/System.Management.Automation/resources/SessionStateStrings.resx @@ -451,7 +451,7 @@ Cannot find a provider with the name '{0}'. - Cannot find a provider with the name '{0}'. The name is not in the proper format. A provider name can only be alphanumeric characters, or a PowerShell Core snap-in name that is followed by a single '\', followed by alphanumeric characters. + Cannot find a provider with the name '{0}'. The name is not in the proper format. A provider name can only be alphanumeric characters, or a PowerShell snap-in name that is followed by a single '\', followed by alphanumeric characters. '{0}' resolved to more than one provider name. Possible matches include:{1}. diff --git a/src/System.Management.Automation/resources/SuggestionStrings.resx b/src/System.Management.Automation/resources/SuggestionStrings.resx index ca8d2a81ed7..66df4cfbdef 100644 --- a/src/System.Management.Automation/resources/SuggestionStrings.resx +++ b/src/System.Management.Automation/resources/SuggestionStrings.resx @@ -124,7 +124,7 @@ The Use-Transaction cmdlet is intended for scripting of transaction-enabled .NET objects. Its ScriptBlock should contain nothing else. - The command {0} was not found, but does exist in the current location. PowerShell Core does not load commands from the current location by default. If you trust this command, instead type: "{1}". See "get-help about_Command_Precedence" for more details. + The command {0} was not found, but does exist in the current location. PowerShell does not load commands from the current location by default. If you trust this command, instead type: "{1}". See "get-help about_Command_Precedence" for more details. Rule must be a ScriptBlock for dynamic match types. diff --git a/src/System.Management.Automation/resources/TypesXmlStrings.resx b/src/System.Management.Automation/resources/TypesXmlStrings.resx index 935061366d4..02c77e45424 100644 --- a/src/System.Management.Automation/resources/TypesXmlStrings.resx +++ b/src/System.Management.Automation/resources/TypesXmlStrings.resx @@ -160,7 +160,7 @@ Cannot create an instance of the type converter for type {0} due to exception: {1}. - PowerShell Core cannot create an instance of the type adapter for the type {0} because of the following exception: {1}. + PowerShell cannot create an instance of the type adapter for the type {0} because of the following exception: {1}. The adapted type "{0}" is not valid. diff --git a/test/powershell/Modules/Microsoft.Powershell.Host/Start-Transcript.Tests.ps1 b/test/powershell/Modules/Microsoft.Powershell.Host/Start-Transcript.Tests.ps1 index 8e15a1bf649..cd5907f87d2 100644 --- a/test/powershell/Modules/Microsoft.Powershell.Host/Start-Transcript.Tests.ps1 +++ b/test/powershell/Modules/Microsoft.Powershell.Host/Start-Transcript.Tests.ps1 @@ -133,7 +133,7 @@ Describe "Start-Transcript, Stop-Transcript tests" -tags "CI" { Test-Path $transcriptFilePath | Should be $true $transcriptFilePath | Should contain "Before Dispose" - $transcriptFilePath | Should contain "PowerShell Core transcript end" + $transcriptFilePath | Should contain "PowerShell transcript end" } } \ No newline at end of file From 2f0967342f29d16e1968b48caebbb6b199ede7b7 Mon Sep 17 00:00:00 2001 From: iSazonov Date: Thu, 7 Sep 2017 14:55:06 +0300 Subject: [PATCH 4/4] Revert 'Core' in some messages --- .../resources/NewObjectStrings.resx | 2 +- .../resources/HostInterfaceExceptionsStrings.resx | 2 +- src/System.Management.Automation/resources/Modules.resx | 2 +- .../resources/MshSnapInCmdletResources.resx | 2 +- .../resources/MshSnapinInfo.resx | 2 +- .../resources/ParserStrings.resx | 6 +++--- .../resources/RemotingErrorIdStrings.resx | 8 ++++---- 7 files changed, 12 insertions(+), 12 deletions(-) diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/NewObjectStrings.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/NewObjectStrings.resx index e8064bfe483..cce49c375f9 100644 --- a/src/Microsoft.PowerShell.Commands.Utility/resources/NewObjectStrings.resx +++ b/src/Microsoft.PowerShell.Commands.Utility/resources/NewObjectStrings.resx @@ -142,6 +142,6 @@ Cannot create type. Only core types are supported in this language mode. - {0} Please note that Single-Threaded Apartment is not supported in PowerShell. + {0} Please note that Single-Threaded Apartment is not supported in PowerShell Core. diff --git a/src/System.Management.Automation/resources/HostInterfaceExceptionsStrings.resx b/src/System.Management.Automation/resources/HostInterfaceExceptionsStrings.resx index 7ad809008c9..eb774f83a01 100644 --- a/src/System.Management.Automation/resources/HostInterfaceExceptionsStrings.resx +++ b/src/System.Management.Automation/resources/HostInterfaceExceptionsStrings.resx @@ -121,7 +121,7 @@ An error of type "{0}" has occurred. - A command that prompts the user failed because the host program or the command type does not support user interaction. Try a host program that supports user interaction, such as the PowerShell Console, and remove prompt-related commands from command types that do not support user interaction, such as PowerShell workflows. + A command that prompts the user failed because the host program or the command type does not support user interaction. Try a host program that supports user interaction, such as the PowerShell Console, and remove prompt-related commands from command types that do not support user interaction. A command that prompts the user failed because the host program or the command type does not support user interaction. The host was attempting to request confirmation with the following message: {0} diff --git a/src/System.Management.Automation/resources/Modules.resx b/src/System.Management.Automation/resources/Modules.resx index c46d41e3c11..53f87e7b959 100644 --- a/src/System.Management.Automation/resources/Modules.resx +++ b/src/System.Management.Automation/resources/Modules.resx @@ -625,7 +625,7 @@ The specified module '{0}' was not found. Update the Name parameter to point to a valid path, and then try again. - Cannot load the workflow module '{0}'. Workflow is not supported in PowerShell. + Cannot load the workflow module '{0}'. Workflow is not supported in PowerShell Core. Populating RepositorySourceLocation property for module {0}. diff --git a/src/System.Management.Automation/resources/MshSnapInCmdletResources.resx b/src/System.Management.Automation/resources/MshSnapInCmdletResources.resx index 5535ffd850a..d23249ed109 100644 --- a/src/System.Management.Automation/resources/MshSnapInCmdletResources.resx +++ b/src/System.Management.Automation/resources/MshSnapInCmdletResources.resx @@ -130,6 +130,6 @@ Cannot add PowerShell snap-in {0} because it is a system PowerShell module. Use Import-Module to load the module. - The custom PowerShell snap-in is not supported in PowerShell. + The custom PowerShell snap-in is not supported in PowerShell Core. diff --git a/src/System.Management.Automation/resources/MshSnapinInfo.resx b/src/System.Management.Automation/resources/MshSnapinInfo.resx index 874fe8a9930..916a4ea3891 100644 --- a/src/System.Management.Automation/resources/MshSnapinInfo.resx +++ b/src/System.Management.Automation/resources/MshSnapinInfo.resx @@ -121,7 +121,7 @@ Unable to access PowerShell registry information. - Unable to access PowerShell PowerShellEngine registry information. + Unable to access PowerShell Engine registry information. Unable to access PublicKeyToken information. diff --git a/src/System.Management.Automation/resources/ParserStrings.resx b/src/System.Management.Automation/resources/ParserStrings.resx index 3c19d7387ec..c8f57cf71aa 100644 --- a/src/System.Management.Automation/resources/ParserStrings.resx +++ b/src/System.Management.Automation/resources/ParserStrings.resx @@ -1192,7 +1192,7 @@ ModuleVersion : Version of module to import. If used, ModuleName must represent Exception occurred when post-parsing dynamic keyword '{0}' with details '{1}'. - Workflow is not supported in PowerShell. + Workflow is not supported in PowerShell Core. Meta Configuration resource {0} is not allowed in the regular configuration. Use meta configuration resources in a configuration with [DscLocalConfigurationManager()] attribute. @@ -1261,7 +1261,7 @@ ModuleVersion : Version of module to import. If used, ModuleName must represent Variant.GetAccessor cannot handle {0}. - Configuration keyword is not supported in PowerShell. + Configuration keyword is not supported in PowerShell Core. Not all code path returns value within method. @@ -1355,7 +1355,7 @@ ModuleVersion : Version of module to import. If used, ModuleName must represent '{1}'. - Cannot run a document in PowerShell: {0}. + Cannot run a document in PowerShell Core: {0}. Multiple type constraints are not allowed on a method parameter. diff --git a/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx b/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx index 7eb96d7d2f3..c31b32e13df 100644 --- a/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx +++ b/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx @@ -657,10 +657,10 @@ Session configuration "{0}" is not a PowerShell-based shell. - Session configuration "{0}" is a PowerShell-based shell. Please use PowerShell to modify it. + Session configuration "{0}" is a PowerShell Core-based shell. Please use PowerShell Core to modify it. - Session configuration "{0}" is a PowerShell-based shell. Please use PowerShell to modify it. + Session configuration "{0}" is a Windows PowerShell-based shell. Please use Windows PowerShell to modify it. No session configuration matches criteria "{0}". @@ -952,7 +952,7 @@ All WinRM sessions connected to PowerShell session configurations, such as Micro A running command could not be found for this PSSession. - The Microsoft .NET Framework 2.0, which is required for PowerShell 2.0, is not installed. Install the .NET Framework 2.0 and retry. + The Microsoft .NET Framework 2.0, which is required for Windows PowerShell 2.0, is not installed. Install the .NET Framework 2.0 and retry. The remote pipeline failed. @@ -1646,7 +1646,7 @@ All WinRM sessions connected to PowerShell session configurations, such as Micro The SSH transport process has abruptly terminated causing this remote session to break. - PowerShell does not support WOW64. The binary must match the architecture of the processor. + PowerShell Core does not support WOW64. The binary must match the architecture of the processor. Unable to install plugin {0} to directory {1}.